You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Jim Apple <jb...@cloudera.com> on 2016/09/06 20:28:03 UTC
Re: Contributions to Cloudera Impala
Any luck with this?
On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple <jb...@cloudera.com> wrote:
> That sounds to me like a network config issue.
>
> As far as what the code should be based on, the Apache repo and the gerrit
> repo should be close, with apache being a few commits behind at most. I use
> gerrit almost exclusively, because that way I know my patches will be based
> on the most recent tree.
>
> On Mon, Aug 22, 2016 at 5:20 AM, Nishidha Panpaliya <ni...@us.ibm.com>
> wrote:
>
>> Hi Jim,
>>
>> We tried the steps mentioned at https://cwiki.apache.org/confl
>> uence/display/IMPALA/How+to+switch+to+Apache-hosted+git.
>> On Cloudera's Impala source tree ->
>> $git remote add apache https://git-wip-us.apache.org/
>> repos/asf/incubator-impala.git
>> $git remote add asf-gerrit ssh://npanpaliya@gerrit.cloude
>> ra.org:29418/Impala-ASF
>> (Here, npanpaliya is my github id which I also used for gerrit login,
>> also added my ssh key to my gerrit settings)
>> $git fetch asf-gerrit
>> ssh: Could not resolve hostname gerrit.cloudera.org:29418: Name or
>> service not known
>>
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.
>>
>>
>> Could you please help us with this error?
>>
>> Our understanding is we need repo referred by "asf-gerrit" only for
>> uploading gerrit code reviews. To work (build, modify, port, test) on
>> actual Impala code base, we still have to follow the steps at
>> https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala. that
>> uses code base referred by "apache" remote.
>>
>> Thanks,
>> Nishidha
>>
>> [image: Inactive hide details for Jim Apple ---08/19/2016 08:58:00 PM--->
>> [Nishidha] We found two new source code URLs as one mentioned]Jim Apple
>> ---08/19/2016 08:58:00 PM---> [Nishidha] We found two new source code URLs
>> as one mentioned in Confluence > https://git-wip-us.a
>>
>> From: Jim Apple <jb...@cloudera.com>
>> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
>> Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
>> Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <sr...@cloudera.com>, Valencia
>> Serrao/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
>> Zhi Zhi NY Yang <zh...@cn.ibm.com>
>> Date: 08/19/2016 08:58 PM
>> Subject: Re: Contributions to Cloudera Impala
>> ------------------------------
>>
>>
>>
>> > [Nishidha] We found two new source code URLs as one mentioned in
>> Confluence
>> > https://git-wip-us.apache.org/repos/asf/incubator-impala.git and
>> another to
>> > be https://github.com/apache/incubator-impala.
>> > Commits wise both look same, though former one says "wip" in the URL.
>> Please
>> > suggest the URL to be forked and worked upon.
>>
>> I don't know exactly what you mean by "forked" in this context. You
>> should use the repo referred to as "asf-gerrit" in
>> https://cwiki.apache.org/confluence/display/IMPALA/How+to+
>> switch+to+Apache-hosted+git
>>
>> > [Nishidha] Okay. So, after CLA, can we work directly on Apache's Impala
>> or
>> > we'll need to fork it into our repository and create a new branch from
>> > master, and then generate PRs/Gerrit code reviews from it?
>>
>> I don't understand this question, but let me try and clarify some
>> things that may help you answer it.
>>
>> All of Impala's commits get code reviews on gerrit.
>>
>> We don't use PRs.
>>
>> > [Nishidha] Which CI do you have or working on?
>>
>> Cloudera uses Jenkins.
>>
>> > What is the expected timeline for your CI to be publicly available?
>>
>> You can follow https://issues.cloudera.org/browse/IMPALA-3228 to learn
>> about updates.
>>
>> Apache projects are sometimes referred to as "do-ocracies". If you
>> would like to find a CI hosting provider that will support Apache
>> Impala, you are welcome to help - you don't have to be an Impala
>> committer or a CLoudera employee to help.
>>
>> > 1. Would you suggest me to start a new thread for branch discussion,
>> > although I created a gist in github.com
>> > https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723 for
>> the
>> > same?
>>
>> Yes. Apache Impala project direction discussions are unlikely to
>> happen on private gists.
>>
>>
>>
>>
>
Re: Contributions to Cloudera Impala
Posted by Lars Volker <lv...@cloudera.com>.
Hi Nishidha,
It looks to me like this URL will be ok to check-out. However you might run
into issues when trying to push your changes, since the URL you used does
not contain a username. The project overview (
https://gerrit.cloudera.org/#/admin/projects/Impala-ASF) has ready-to-copy
URLs for various ways of accessing the repo.
Your original problem ("Could not resolve hostname") sounds like a DNS
configuration issue to me. Once you're able to connect to the HTTP endpoint
you might want to give this one another try and see if you're able to
connect now.
Cheers, Lars
On Fri, Sep 9, 2016 at 8:33 AM, Nishidha Panpaliya <ni...@us.ibm.com>
wrote:
> Hi Jim,
>
> I checked the links you shared. Also tried http://gerrit.cloudera.org/
> ssh_info in the browser and it worked. However, curl
> http://gerrit.cloudera.org/ssh_info <http://%27hostname%27/ssh_info> is
> not working from git bash for some unknown reason giving timeout error. We
> also checked with our IT personnel and he has unblocked the port 29418 too,
> but still getting same error. It looks like ssh url repo has some issues
> for us.
>
> However, I'm able to clone or fetch code from the same repo using HTTP
> http://gerrit.cloudera.org:8080/Impala-ASF.
> Please let us know if this is okay to proceed.
>
> Thanks,
> Nishidha
>
> [image: Inactive hide details for Jim Apple ---09/09/2016 09:50:30 AM---I
> do not know if any such method is possible. Did you read http]Jim Apple
> ---09/09/2016 09:50:30 AM---I do not know if any such method is possible.
> Did you read https://review.openstack.org/Documentatio
>
> From: Jim Apple <jb...@cloudera.com>
> To: Valencia Serrao/Austin/Contr/IBM@IBMUS
> Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
> Patil/Austin/Contr/IBM@IBMUS, Nishidha Panpaliya/Austin/Contr/IBM@IBMUS,
> Silvius Rus <sr...@cloudera.com>, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
> Zhi Zhi NY Yang <zh...@cn.ibm.com>
> Date: 09/09/2016 09:50 AM
>
> Subject: Re: Contributions to Cloudera Impala
> ------------------------------
>
>
>
> I do not know if any such method is possible. Did you read
> *https://review.openstack.org/Documentation/user-upload.html*
> <https://review.openstack.org/Documentation/user-upload.html>? Did you
> try anything on it?
>
> Have you tried debugging your ssh issues? Did you talk to your network
> config people?
>
> On Thu, Sep 8, 2016 at 9:02 PM, Valencia Serrao <*vserrao@us.ibm.com*
> <vs...@us.ibm.com>> wrote:
>
> Hi Jim,
>
> Thanks for you concern.
>
> Looks like we are having some issues while accessing the ssh URL,
> could you please provide us the equivalent https link for the asf-gerrit
> remote ?
>
>
> Regards,
> Valencia
>
>
> [image: Inactive hide details for Jim Apple ---09/07/2016 01:58:53
> AM---Any luck with this? On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple]Jim
> Apple ---09/07/2016 01:58:53 AM---Any luck with this? On Thu, Aug 25, 2016
> at 10:47 AM, Jim Apple <*jbapple@cloudera.com* <jb...@cloudera.com>>
> wrote:
>
> From: Jim Apple <*jbapple@cloudera.com* <jb...@cloudera.com>>
> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
> Cc: "dev@impala" <*dev@impala.incubator.apache.org*
> <de...@impala.incubator.apache.org>>, Manish Patil/Austin/Contr/IBM@IBMUS,
> Silvius Rus <*srus@cloudera.com* <sr...@cloudera.com>>, Valencia
> Serrao/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
> Zhi Zhi NY Yang <*zhizhiy@cn.ibm.com* <zh...@cn.ibm.com>>
> Date: 09/07/2016 01:58 AM
> Subject: Re: Contributions to Cloudera Impala
> ------------------------------
>
>
>
> Any luck with this?
>
> On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple <*jbapple@cloudera.com*
> <jb...@cloudera.com>> wrote:
> That sounds to me like a network config issue.
>
> As far as what the code should be based on, the Apache repo and
> the gerrit repo should be close, with apache being a few commits behind at
> most. I use gerrit almost exclusively, because that way I know my patches
> will be based on the most recent tree.
>
> On Mon, Aug 22, 2016 at 5:20 AM, Nishidha Panpaliya <
> *nishidha@us.ibm.com* <ni...@us.ibm.com>> wrote:
> Hi Jim,
>
> We tried the steps mentioned at
> *https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git*
> <https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git>
> .
> On Cloudera's Impala source tree ->
> $git remote add apache
> *https://git-wip-us.apache.org/repos/asf/incubator-impala.git*
> <https://git-wip-us.apache.org/repos/asf/incubator-impala.git>
> $git remote add asf-gerrit ssh://
> *npanpaliya@gerrit.cloudera.org:29418/Impala-ASF*
> <http://npanpaliya@gerrit.cloudera.org:29418/Impala-ASF>
> (Here, npanpaliya is my github id which I also used for gerrit
> login, also added my ssh key to my gerrit settings)
> $git fetch asf-gerrit
> ssh: Could not resolve hostname *gerrit.cloudera.org:29418*
> <http://gerrit.cloudera.org:29418/>: Name or service not known
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct
> access rights
> and the repository exists.
>
> Could you please help us with this error?
>
> Our understanding is we need repo referred by "asf-gerrit" only
> for uploading gerrit code reviews. To work (build, modify, port, test) on
> actual Impala code base, we still have to follow the steps at
> *https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala*
> <https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala>.
> that uses code base referred by "apache" remote.
>
> Thanks,
> Nishidha
>
> Jim Apple ---08/19/2016 08:58:00 PM---> [Nishidha] We found two
> new source code URLs as one mentioned in Confluence >
> *https://git-wip-us.a* <https://git-wip-us.a/>
>
> From: Jim Apple <*jbapple@cloudera.com* <jb...@cloudera.com>>
> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
> Cc: "dev@impala" <*dev@impala.incubator.apache.org*
> <de...@impala.incubator.apache.org>>, Manish
> Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <*srus@cloudera.com*
> <sr...@cloudera.com>>, Valencia Serrao/Austin/Contr/IBM@IBMUS,
> Sudarshan Jagadale/Austin/Contr/IBM@IBMUS, Zhi Zhi NY Yang <
> *zhizhiy@cn.ibm.com* <zh...@cn.ibm.com>>
> Date: 08/19/2016 08:58 PM
> Subject: Re: Contributions to Cloudera Impala
> ------------------------------
>
>
>
> > [Nishidha] We found two new source code URLs as one mentioned
> in Confluence
> > *https://git-wip-us.apache.org/repos/asf/incubator-impala.git*
> <https://git-wip-us.apache.org/repos/asf/incubator-impala.git> and
> another to
> > be *https://github.com/apache/incubator-impala*
> <https://github.com/apache/incubator-impala>.
> > Commits wise both look same, though former one says "wip" in
> the URL. Please
> > suggest the URL to be forked and worked upon.
>
> I don't know exactly what you mean by "forked" in this context.
> You
> should use the repo referred to as "asf-gerrit" in
>
> *https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git*
> <https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git>
>
> > [Nishidha] Okay. So, after CLA, can we work directly on
> Apache's Impala or
> > we'll need to fork it into our repository and create a new
> branch from
> > master, and then generate PRs/Gerrit code reviews from it?
>
> I don't understand this question, but let me try and clarify some
> things that may help you answer it.
>
> All of Impala's commits get code reviews on gerrit.
>
> We don't use PRs.
>
> > [Nishidha] Which CI do you have or working on?
>
> Cloudera uses Jenkins.
>
> > What is the expected timeline for your CI to be publicly
> available?
>
> You can follow *https://issues.cloudera.org/browse/IMPALA-3228*
> <https://issues.cloudera.org/browse/IMPALA-3228> to learn
> about updates.
>
> Apache projects are sometimes referred to as "do-ocracies". If
> you
> would like to find a CI hosting provider that will support Apache
> Impala, you are welcome to help - you don't have to be an Impala
> committer or a CLoudera employee to help.
>
> > 1. Would you suggest me to start a new thread for branch
> discussion,
> > although I created a gist in *github.com* <http://github.com/>
> >
> *https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723*
> <https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723> for
> the
> > same?
>
> Yes. Apache Impala project direction discussions are unlikely to
> happen on private gists.
>
>
>
>
>
>
>
Re: Contributions to Cloudera Impala
Posted by Nishidha Panpaliya <ni...@us.ibm.com>.
Hi Jim,
I checked the links you shared. Also tried
http://gerrit.cloudera.org/ssh_info in the browser and it worked. However,
curl http://gerrit.cloudera.org/ssh_info is not working from git bash for
some unknown reason giving timeout error. We also checked with our IT
personnel and he has unblocked the port 29418 too, but still getting same
error. It looks like ssh url repo has some issues for us.
However, I'm able to clone or fetch code from the same repo using HTTP
http://gerrit.cloudera.org:8080/Impala-ASF.
Please let us know if this is okay to proceed.
Thanks,
Nishidha
From: Jim Apple <jb...@cloudera.com>
To: Valencia Serrao/Austin/Contr/IBM@IBMUS
Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
Patil/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS, Silvius Rus
<sr...@cloudera.com>, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
Zhi Zhi NY Yang <zh...@cn.ibm.com>
Date: 09/09/2016 09:50 AM
Subject: Re: Contributions to Cloudera Impala
I do not know if any such method is possible. Did you read
https://review.openstack.org/Documentation/user-upload.html? Did you try
anything on it?
Have you tried debugging your ssh issues? Did you talk to your network
config people?
On Thu, Sep 8, 2016 at 9:02 PM, Valencia Serrao <vs...@us.ibm.com> wrote:
Hi Jim,
Thanks for you concern.
Looks like we are having some issues while accessing the ssh URL, could
you please provide us the equivalent https link for the asf-gerrit
remote ?
Regards,
Valencia
Inactive hide details for Jim Apple ---09/07/2016 01:58:53 AM---Any luck
with this? On Thu, Aug 25, 2016 at 10:47 AM, Jim AppleJim Apple
---09/07/2016 01:58:53 AM---Any luck with this? On Thu, Aug 25, 2016 at
10:47 AM, Jim Apple <jb...@cloudera.com> wrote:
From: Jim Apple <jb...@cloudera.com>
To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <sr...@cloudera.com>, Valencia
Serrao/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
Zhi Zhi NY Yang <zh...@cn.ibm.com>
Date: 09/07/2016 01:58 AM
Subject: Re: Contributions to Cloudera Impala
Any luck with this?
On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple <jb...@cloudera.com> wrote:
That sounds to me like a network config issue.
As far as what the code should be based on, the Apache repo and the
gerrit repo should be close, with apache being a few commits behind
at most. I use gerrit almost exclusively, because that way I know
my patches will be based on the most recent tree.
On Mon, Aug 22, 2016 at 5:20 AM, Nishidha Panpaliya <
nishidha@us.ibm.com> wrote:
Hi Jim,
We tried the steps mentioned at
https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to
+Apache-hosted+git.
On Cloudera's Impala source tree ->
$git remote add apache
https://git-wip-us.apache.org/repos/asf/incubator-impala.git
$git remote add asf-gerrit ssh://
npanpaliya@gerrit.cloudera.org:29418/Impala-ASF
(Here, npanpaliya is my github id which I also used for gerrit
login, also added my ssh key to my gerrit settings)
$git fetch asf-gerrit
ssh: Could not resolve hostname gerrit.cloudera.org:29418: Name or
service not known
fatal: Could not read from remote
repository.
Please make sure you have the correct
access rights
and the repository exists.
Could you please help us with this error?
Our understanding is we need repo referred by "asf-gerrit" only for
uploading gerrit code reviews. To work (build, modify, port, test)
on actual Impala code base, we still have to follow the steps at
https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala.
that uses code base referred by "apache" remote.
Thanks,
Nishidha
Jim Apple ---08/19/2016 08:58:00 PM---> [Nishidha] We found two new
source code URLs as one mentioned in Confluence >
https://git-wip-us.a
From: Jim Apple <jb...@cloudera.com>
To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <sr...@cloudera.com>,
Valencia Serrao/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Zhi Zhi NY Yang <
zhizhiy@cn.ibm.com>
Date: 08/19/2016 08:58 PM
Subject: Re: Contributions to Cloudera Impala
> [Nishidha] We found two new source code URLs as one mentioned in
Confluence
> https://git-wip-us.apache.org/repos/asf/incubator-impala.git and
another to
> be https://github.com/apache/incubator-impala.
> Commits wise both look same, though former one says "wip" in the
URL. Please
> suggest the URL to be forked and worked upon.
I don't know exactly what you mean by "forked" in this context. You
should use the repo referred to as "asf-gerrit" in
https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to
+Apache-hosted+git
> [Nishidha] Okay. So, after CLA, can we work directly on Apache's
Impala or
> we'll need to fork it into our repository and create a new branch
from
> master, and then generate PRs/Gerrit code reviews from it?
I don't understand this question, but let me try and clarify some
things that may help you answer it.
All of Impala's commits get code reviews on gerrit.
We don't use PRs.
> [Nishidha] Which CI do you have or working on?
Cloudera uses Jenkins.
> What is the expected timeline for your CI to be publicly
available?
You can follow https://issues.cloudera.org/browse/IMPALA-3228 to
learn
about updates.
Apache projects are sometimes referred to as "do-ocracies". If you
would like to find a CI hosting provider that will support Apache
Impala, you are welcome to help - you don't have to be an Impala
committer or a CLoudera employee to help.
> 1. Would you suggest me to start a new thread for branch
discussion,
> although I created a gist in github.com
>
https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723
for the
> same?
Yes. Apache Impala project direction discussions are unlikely to
happen on private gists.
Re: Contributions to Cloudera Impala
Posted by Jim Apple <jb...@cloudera.com>.
I do not know if any such method is possible. Did you read
https://review.openstack.org/Documentation/user-upload.html? Did you try
anything on it?
Have you tried debugging your ssh issues? Did you talk to your network
config people?
On Thu, Sep 8, 2016 at 9:02 PM, Valencia Serrao <vs...@us.ibm.com> wrote:
> Hi Jim,
>
> Thanks for you concern.
>
> Looks like we are having some issues while accessing the ssh URL, could
> you please provide us the equivalent https link for the asf-gerrit remote ?
>
>
> Regards,
> Valencia
>
>
> [image: Inactive hide details for Jim Apple ---09/07/2016 01:58:53
> AM---Any luck with this? On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple]Jim
> Apple ---09/07/2016 01:58:53 AM---Any luck with this? On Thu, Aug 25, 2016
> at 10:47 AM, Jim Apple <jb...@cloudera.com> wrote:
>
> From: Jim Apple <jb...@cloudera.com>
> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
> Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
> Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <sr...@cloudera.com>, Valencia
> Serrao/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
> Zhi Zhi NY Yang <zh...@cn.ibm.com>
> Date: 09/07/2016 01:58 AM
> Subject: Re: Contributions to Cloudera Impala
> ------------------------------
>
>
>
> Any luck with this?
>
> On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple <*jbapple@cloudera.com*
> <jb...@cloudera.com>> wrote:
>
> That sounds to me like a network config issue.
>
> As far as what the code should be based on, the Apache repo and the
> gerrit repo should be close, with apache being a few commits behind at
> most. I use gerrit almost exclusively, because that way I know my patches
> will be based on the most recent tree.
>
> On Mon, Aug 22, 2016 at 5:20 AM, Nishidha Panpaliya <
> *nishidha@us.ibm.com* <ni...@us.ibm.com>> wrote:
> Hi Jim,
>
> We tried the steps mentioned at
> *https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git*
> <https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git>
> .
> On Cloudera's Impala source tree ->
> $git remote add apache
> *https://git-wip-us.apache.org/repos/asf/incubator-impala.git*
> <https://git-wip-us.apache.org/repos/asf/incubator-impala.git>
> $git remote add asf-gerrit ssh://
> *npanpaliya@gerrit.cloudera.org:29418/Impala-ASF*
> <http://npanpaliya@gerrit.cloudera.org:29418/Impala-ASF>
> (Here, npanpaliya is my github id which I also used for gerrit login,
> also added my ssh key to my gerrit settings)
> $git fetch asf-gerrit
> ssh: Could not resolve hostname *gerrit.cloudera.org:29418*
> <http://gerrit.cloudera.org:29418/>: Name or service not known
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Could you please help us with this error?
>
> Our understanding is we need repo referred by "asf-gerrit" only for
> uploading gerrit code reviews. To work (build, modify, port, test) on
> actual Impala code base, we still have to follow the steps at
> *https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala*
> <https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala>.
> that uses code base referred by "apache" remote.
>
> Thanks,
> Nishidha
>
> Jim Apple ---08/19/2016 08:58:00 PM---> [Nishidha] We found two new
> source code URLs as one mentioned in Confluence >
> *https://git-wip-us.a* <https://git-wip-us.a/>
>
> From: Jim Apple <*jbapple@cloudera.com* <jb...@cloudera.com>>
> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
> Cc: "dev@impala" <*dev@impala.incubator.apache.org*
> <de...@impala.incubator.apache.org>>, Manish Patil/Austin/Contr/IBM@IBMUS,
> Silvius Rus <*srus@cloudera.com* <sr...@cloudera.com>>, Valencia
> Serrao/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS,
> Zhi Zhi NY Yang <*zhizhiy@cn.ibm.com* <zh...@cn.ibm.com>>
> Date: 08/19/2016 08:58 PM
> Subject: Re: Contributions to Cloudera Impala
> ------------------------------
>
>
>
> > [Nishidha] We found two new source code URLs as one mentioned in
> Confluence
> > *https://git-wip-us.apache.org/repos/asf/incubator-impala.git*
> <https://git-wip-us.apache.org/repos/asf/incubator-impala.git> and
> another to
> > be *https://github.com/apache/incubator-impala*
> <https://github.com/apache/incubator-impala>.
> > Commits wise both look same, though former one says "wip" in the
> URL. Please
> > suggest the URL to be forked and worked upon.
>
> I don't know exactly what you mean by "forked" in this context. You
> should use the repo referred to as "asf-gerrit" in
>
> *https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git*
> <https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to+Apache-hosted+git>
>
> > [Nishidha] Okay. So, after CLA, can we work directly on Apache's
> Impala or
> > we'll need to fork it into our repository and create a new branch
> from
> > master, and then generate PRs/Gerrit code reviews from it?
>
> I don't understand this question, but let me try and clarify some
> things that may help you answer it.
>
> All of Impala's commits get code reviews on gerrit.
>
> We don't use PRs.
>
> > [Nishidha] Which CI do you have or working on?
>
> Cloudera uses Jenkins.
>
> > What is the expected timeline for your CI to be publicly available?
>
> You can follow *https://issues.cloudera.org/browse/IMPALA-3228*
> <https://issues.cloudera.org/browse/IMPALA-3228> to learn
> about updates.
>
> Apache projects are sometimes referred to as "do-ocracies". If you
> would like to find a CI hosting provider that will support Apache
> Impala, you are welcome to help - you don't have to be an Impala
> committer or a CLoudera employee to help.
>
> > 1. Would you suggest me to start a new thread for branch discussion,
> > although I created a gist in *github.com* <http://github.com/>
> > *https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723*
> <https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723> for
> the
> > same?
>
> Yes. Apache Impala project direction discussions are unlikely to
> happen on private gists.
>
>
>
>
>
>
>
Re: Contributions to Cloudera Impala
Posted by Valencia Serrao <vs...@us.ibm.com>.
Hi Jim,
Thanks for you concern.
Looks like we are having some issues while accessing the ssh URL, could you
please provide us the equivalent https link for the asf-gerrit remote ?
Regards,
Valencia
From: Jim Apple <jb...@cloudera.com>
To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <sr...@cloudera.com>,
Valencia Serrao/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Zhi Zhi NY Yang
<zh...@cn.ibm.com>
Date: 09/07/2016 01:58 AM
Subject: Re: Contributions to Cloudera Impala
Any luck with this?
On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple <jb...@cloudera.com> wrote:
That sounds to me like a network config issue.
As far as what the code should be based on, the Apache repo and the
gerrit repo should be close, with apache being a few commits behind at
most. I use gerrit almost exclusively, because that way I know my patches
will be based on the most recent tree.
On Mon, Aug 22, 2016 at 5:20 AM, Nishidha Panpaliya <ni...@us.ibm.com>
wrote:
Hi Jim,
We tried the steps mentioned at
https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to
+Apache-hosted+git.
On Cloudera's Impala source tree ->
$git remote add apache
https://git-wip-us.apache.org/repos/asf/incubator-impala.git
$git remote add asf-gerrit ssh://
npanpaliya@gerrit.cloudera.org:29418/Impala-ASF
(Here, npanpaliya is my github id which I also used for gerrit login,
also added my ssh key to my gerrit settings)
$git fetch asf-gerrit
ssh: Could not resolve hostname gerrit.cloudera.org:29418: Name or
service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could you please help us with this error?
Our understanding is we need repo referred by "asf-gerrit" only for
uploading gerrit code reviews. To work (build, modify, port, test) on
actual Impala code base, we still have to follow the steps at
https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala. that
uses code base referred by "apache" remote.
Thanks,
Nishidha
Jim Apple ---08/19/2016 08:58:00 PM---> [Nishidha] We found two new
source code URLs as one mentioned in Confluence > https://git-wip-us.a
From: Jim Apple <jb...@cloudera.com>
To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS
Cc: "dev@impala" <de...@impala.incubator.apache.org>, Manish
Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <sr...@cloudera.com>, Valencia
Serrao/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Zhi Zhi NY Yang <zh...@cn.ibm.com>
Date: 08/19/2016 08:58 PM
Subject: Re: Contributions to Cloudera Impala
> [Nishidha] We found two new source code URLs as one mentioned in
Confluence
> https://git-wip-us.apache.org/repos/asf/incubator-impala.git and
another to
> be https://github.com/apache/incubator-impala.
> Commits wise both look same, though former one says "wip" in the URL.
Please
> suggest the URL to be forked and worked upon.
I don't know exactly what you mean by "forked" in this context. You
should use the repo referred to as "asf-gerrit" in
https://cwiki.apache.org/confluence/display/IMPALA/How+to+switch+to
+Apache-hosted+git
> [Nishidha] Okay. So, after CLA, can we work directly on Apache's
Impala or
> we'll need to fork it into our repository and create a new branch from
> master, and then generate PRs/Gerrit code reviews from it?
I don't understand this question, but let me try and clarify some
things that may help you answer it.
All of Impala's commits get code reviews on gerrit.
We don't use PRs.
> [Nishidha] Which CI do you have or working on?
Cloudera uses Jenkins.
> What is the expected timeline for your CI to be publicly available?
You can follow https://issues.cloudera.org/browse/IMPALA-3228 to learn
about updates.
Apache projects are sometimes referred to as "do-ocracies". If you
would like to find a CI hosting provider that will support Apache
Impala, you are welcome to help - you don't have to be an Impala
committer or a CLoudera employee to help.
> 1. Would you suggest me to start a new thread for branch discussion,
> although I created a gist in github.com
> https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723
for the
> same?
Yes. Apache Impala project direction discussions are unlikely to
happen on private gists.