drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From prasanna pradhan <prasa...@datarpm.com>
Subject Re: Please suggest the necessary steps to commit changes into the drill codebase
Date Thu, 11 Dec 2014 10:55:22 GMT
Thanks Aditya got it !

Hbase Uni Container:
It is an existing component in datarpm application which encapsulates 
the hbase implementation by vendor, platform etc and provides a unified 
hbase interaction layer.
We are trying to make a custom hbase storage plugin which can support 
vendor and version independent hbase interaction.

Would like to try it in local environment and an internal team on 
whether it is possible to integrate with drill at this stage.
We have not been an active members in drill community but are ardent 
followers so do not know the right path to follow in this aspect.

We are comfortable with coding and hence the first intention was to jump 
in and code.
Please suggest approaches as necessary.


On Thursday 11 December 2014 04:13 PM, Aditya wrote:
> Hi Prasanna,
> The most common way would be to create your personal fork of Drill's GitHub
> repository[1] and create branch in that.
> Once the feature is somewhat mature, you can export the patch and upload it
> to Apache review board[2].
> Btw, what exactly do you mean by unified HBase Gateway? It might be useful
> to discuss the idea and design on the dev list before stating the
> implantation.
> aditya...
> [1] https://github.com/apache/drill
> [2] https://reviews.apache.org/dashboard/
> On Thu, Dec 11, 2014 at 12:48 AM, prasanna pradhan <prasanna@datarpm.com>
> wrote:
>> Hi Team,
>> I need to create a new branch to add a unified HBase Gateway plugin to
>> drill platform. I do not have access rights to do so.
>> Can you please help me with access / process by which I may be able to
>> check in code.
>> Thanks,
>> Prasanna

View raw message