You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by prasanna pradhan <pr...@datarpm.com> on 2014/12/11 09:48:37 UTC
Please suggest the necessary steps to commit changes into the drill
codebase
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
Re: Please suggest the necessary steps to commit changes into the
drill codebase
Posted by prasanna pradhan <pr...@datarpm.com>.
Abel,
Thanks a lot. This is exactly what I was looking for.
Sincerely appreciate.
-Prasanna
On Thursday 11 December 2014 08:52 PM, Abdel Hakim Deneche wrote:
> Hello Prasanna,
>
> The following wiki page has all the informations you need to contribute to
> Drill:
>
> https://cwiki.apache.org/confluence/display/DRILL/Apache+Drill+Contribution+Guidelines
>
> If you decide to create a fork, which is recommended, you need to add
> another remote to your repository. The following links explain exactly how
> to do this:
> https://help.github.com/articles/configuring-a-remote-for-a-fork/
> https://help.github.com/articles/syncing-a-fork/
>
> Thanks,
> Hakim
>
> On Thu, Dec 11, 2014 at 2:59 AM, prasanna pradhan <pr...@datarpm.com>
> wrote:
>
>> One more thing Aditya.
>>
>> If we fork from the main branch then how do we get the latest changes from
>> the main branch into the forked branch ?
>>
>> Thanks,
>> Prasanna
>>
>>
>> On Thursday 11 December 2014 04:25 PM, prasanna pradhan wrote:
>>
>>> 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.
>>>
>>> Thanks,
>>> Prasanna
>>>
>>>
>>> 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
>>>>>
>>>>>
Re: Please suggest the necessary steps to commit changes into the
drill codebase
Posted by Abdel Hakim Deneche <ad...@maprtech.com>.
Hello Prasanna,
The following wiki page has all the informations you need to contribute to
Drill:
https://cwiki.apache.org/confluence/display/DRILL/Apache+Drill+Contribution+Guidelines
If you decide to create a fork, which is recommended, you need to add
another remote to your repository. The following links explain exactly how
to do this:
https://help.github.com/articles/configuring-a-remote-for-a-fork/
https://help.github.com/articles/syncing-a-fork/
Thanks,
Hakim
On Thu, Dec 11, 2014 at 2:59 AM, prasanna pradhan <pr...@datarpm.com>
wrote:
> One more thing Aditya.
>
> If we fork from the main branch then how do we get the latest changes from
> the main branch into the forked branch ?
>
> Thanks,
> Prasanna
>
>
> On Thursday 11 December 2014 04:25 PM, prasanna pradhan wrote:
>
>> 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.
>>
>> Thanks,
>> Prasanna
>>
>>
>> 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
>>>>
>>>>
>>
>
Re: Please suggest the necessary steps to commit changes into the
drill codebase
Posted by prasanna pradhan <pr...@datarpm.com>.
One more thing Aditya.
If we fork from the main branch then how do we get the latest changes
from the main branch into the forked branch ?
Thanks,
Prasanna
On Thursday 11 December 2014 04:25 PM, prasanna pradhan wrote:
> 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.
>
> Thanks,
> Prasanna
>
>
> 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
>> <pr...@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
>>>
>
Re: Please suggest the necessary steps to commit changes into the
drill codebase
Posted by prasanna pradhan <pr...@datarpm.com>.
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.
Thanks,
Prasanna
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 <pr...@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
>>
Re: Please suggest the necessary steps to commit changes into the
drill codebase
Posted by Aditya <ad...@apache.org>.
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 <pr...@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
>
Re: Please suggest the necessary steps to commit changes into the
drill codebase
Posted by Kristopher Francisco <kr...@me.com>.
Unsubscribe
On Thursday, December 11, 2014, prasanna pradhan <pr...@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
>