Re: New release branch 2.0.0

[Kalyan Kumar Kalvagadda]

I'm observing error while deploying the artifacts in maven repository.
Looks like I don't have permission to do it.

[ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
> Failed to deploy artifacts: Could not transfer artifact
> org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file: https://repository.apache.org/
> service/local/staging/deploy/maven2/org/apache/sentry/
> sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> *Unauthorized*. -> [Help 1]
>


Does any one know if I need some permissions to deploy?

-Kalyan

On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> Sure, I will change the branch to sentry-2.0
>
> Thanks,
> Kalyan
>
> -Kalyan
>
> On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena 
> wrote:
>
>> That's old Kalyan. Why do you propose bringing back the old approach? The
>> new approach is used by other Apache components where bugfix releases are
>> only tags. This reduces the release process and steps of bugfix releases.
>>
>> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
>> kkal...@cloudera.com> wrote:
>>
>> > Sergio,
>> >
>> > If you look at all the previous branches they are followed convention
>> > sentry-major.minor.patch. I tried to be in-line with them.
>> >
>> > -Kalyan
>> >
>> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena 
>> > wrote:
>> >
>> > > Great, thanks Kalyan.
>> > >
>> > > Btw, the branch should be named branch-2.0 as the Wiki suggests (git
>> > > checkout -b branch-1.8). It is better to name a branch this way so we
>> can
>> > > commit bugfixes on it for future 2.0.x bugfix releases.
>> > >
>> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
>> > > kkal...@cloudera.com> wrote:
>> > >
>> > > > I've just created new release branch for upcoming 2.0.0 release.
>> Please
>> > > > continue committing to master branch as usual.
>> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
>> > > >
>> > > > -Kalyan
>> > > >
>> > >
>> >
>>
>
>

Re: New release branch 2.0.0

[Colm O hEigeartaigh]

Have you got a "apache.releases.https" server defined in your maven
settings.xml, with a corresponding username + password?

Colm.

On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> I'm observing error while deploying the artifacts in maven repository.
> Looks like I don't have permission to do it.
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
> > Failed to deploy artifacts: Could not transfer artifact
> > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> > https://repository.apache.org/service/local/staging/deploy/maven2):
> > Failed to transfer file: https://repository.apache.org/
> > service/local/staging/deploy/maven2/org/apache/sentry/
> > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> > *Unauthorized*. -> [Help 1]
> >
>
>
> Does any one know if I need some permissions to deploy?
>
> -Kalyan
>
> On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > Sure, I will change the branch to sentry-2.0
> >
> > Thanks,
> > Kalyan
> >
> > -Kalyan
> >
> > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena 
> > wrote:
> >
> >> That's old Kalyan. Why do you propose bringing back the old approach?
> The
> >> new approach is used by other Apache components where bugfix releases
> are
> >> only tags. This reduces the release process and steps of bugfix
> releases.
> >>
> >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> >> kkal...@cloudera.com> wrote:
> >>
> >> > Sergio,
> >> >
> >> > If you look at all the previous branches they are followed convention
> >> > sentry-major.minor.patch. I tried to be in-line with them.
> >> >
> >> > -Kalyan
> >> >
> >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> sergio.p...@cloudera.com>
> >> > wrote:
> >> >
> >> > > Great, thanks Kalyan.
> >> > >
> >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests (git
> >> > > checkout -b branch-1.8). It is better to name a branch this way so
> we
> >> can
> >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> >> > >
> >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> >> > > kkal...@cloudera.com> wrote:
> >> > >
> >> > > > I've just created new release branch for upcoming 2.0.0 release.
> >> Please
> >> > > > continue committing to master branch as usual.
> >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >> > > >
> >> > > > -Kalyan
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: New release branch 2.0.0

[Sergio Pena]

I have the same issue.

Colm, the wiki mentioned "apache.staging.https". is that the correct one?

On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh 
wrote:

> Have you got a "apache.releases.https" server defined in your maven
> settings.xml, with a corresponding username + password?
>
> Colm.
>
> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > I'm observing error while deploying the artifacts in maven repository.
> > Looks like I don't have permission to do it.
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
> > > Failed to deploy artifacts: Could not transfer artifact
> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> > > https://repository.apache.org/service/local/staging/deploy/maven2):
> > > Failed to transfer file: https://repository.apache.org/
> > > service/local/staging/deploy/maven2/org/apache/sentry/
> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> > > *Unauthorized*. -> [Help 1]
> > >
> >
> >
> > Does any one know if I need some permissions to deploy?
> >
> > -Kalyan
> >
> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> > kkal...@cloudera.com> wrote:
> >
> > > Sure, I will change the branch to sentry-2.0
> > >
> > > Thanks,
> > > Kalyan
> > >
> > > -Kalyan
> > >
> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
> sergio.p...@cloudera.com>
> > > wrote:
> > >
> > >> That's old Kalyan. Why do you propose bringing back the old approach?
> > The
> > >> new approach is used by other Apache components where bugfix releases
> > are
> > >> only tags. This reduces the release process and steps of bugfix
> > releases.
> > >>
> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> > >> kkal...@cloudera.com> wrote:
> > >>
> > >> > Sergio,
> > >> >
> > >> > If you look at all the previous branches they are followed
> convention
> > >> > sentry-major.minor.patch. I tried to be in-line with them.
> > >> >
> > >> > -Kalyan
> > >> >
> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> > sergio.p...@cloudera.com>
> > >> > wrote:
> > >> >
> > >> > > Great, thanks Kalyan.
> > >> > >
> > >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests
> (git
> > >> > > checkout -b branch-1.8). It is better to name a branch this way so
> > we
> > >> can
> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> > >> > >
> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> > >> > > kkal...@cloudera.com> wrote:
> > >> > >
> > >> > > > I've just created new release branch for upcoming 2.0.0 release.
> > >> Please
> > >> > > > continue committing to master branch as usual.
> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> > >> > > >
> > >> > > > -Kalyan
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Re: New release branch 2.0.0

[Colm O hEigeartaigh]

I think it should be "apache.releases.https" based on the error message
below. I have both in my local settings.xml, so you could try adding both
in!

Colm.

On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
wrote:

> I have the same issue.
>
> Colm, the wiki mentioned "apache.staging.https". is that the correct one?
>
> On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh  > wrote:
>
>> Have you got a "apache.releases.https" server defined in your maven
>> settings.xml, with a corresponding username + password?
>>
>> Colm.
>>
>> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
>> kkal...@cloudera.com> wrote:
>>
>> > I'm observing error while deploying the artifacts in maven repository.
>> > Looks like I don't have permission to do it.
>> >
>> > [ERROR] Failed to execute goal org.apache.maven.plugins:
>> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
>> > > Failed to deploy artifacts: Could not transfer artifact
>> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
>> > > https://repository.apache.org/service/local/staging/deploy/maven2):
>> > > Failed to transfer file: https://repository.apache.org/
>> > > service/local/staging/deploy/maven2/org/apache/sentry/
>> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
>> > > *Unauthorized*. -> [Help 1]
>> > >
>> >
>> >
>> > Does any one know if I need some permissions to deploy?
>> >
>> > -Kalyan
>> >
>> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
>> > kkal...@cloudera.com> wrote:
>> >
>> > > Sure, I will change the branch to sentry-2.0
>> > >
>> > > Thanks,
>> > > Kalyan
>> > >
>> > > -Kalyan
>> > >
>> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
>> sergio.p...@cloudera.com>
>> > > wrote:
>> > >
>> > >> That's old Kalyan. Why do you propose bringing back the old approach?
>> > The
>> > >> new approach is used by other Apache components where bugfix releases
>> > are
>> > >> only tags. This reduces the release process and steps of bugfix
>> > releases.
>> > >>
>> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
>> > >> kkal...@cloudera.com> wrote:
>> > >>
>> > >> > Sergio,
>> > >> >
>> > >> > If you look at all the previous branches they are followed
>> convention
>> > >> > sentry-major.minor.patch. I tried to be in-line with them.
>> > >> >
>> > >> > -Kalyan
>> > >> >
>> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
>> > sergio.p...@cloudera.com>
>> > >> > wrote:
>> > >> >
>> > >> > > Great, thanks Kalyan.
>> > >> > >
>> > >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests
>> (git
>> > >> > > checkout -b branch-1.8). It is better to name a branch this way
>> so
>> > we
>> > >> can
>> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
>> > >> > >
>> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
>> > >> > > kkal...@cloudera.com> wrote:
>> > >> > >
>> > >> > > > I've just created new release branch for upcoming 2.0.0
>> release.
>> > >> Please
>> > >> > > > continue committing to master branch as usual.
>> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
>> > >> > > >
>> > >> > > > -Kalyan
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: New release branch 2.0.0

[Kalyan Kumar Kalvagadda]

Colm,

This the the complete content of my settings.xml.
>
> 
>
>   apache.staging.https
>
>   kalyan
>
>   *
>
>apache.releases.https
>
>   kalyan
>
>   *
>
>  
>
>

I'm running below command.

> mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts


I still observe the same issue.

-Kalyan

On Tue, Nov 28, 2017 at 10:46 AM, Colm O hEigeartaigh 
wrote:

> I think it should be "apache.releases.https" based on the error message
> below. I have both in my local settings.xml, so you could try adding both
> in!
>
> Colm.
>
> On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
> wrote:
>
> > I have the same issue.
> >
> > Colm, the wiki mentioned "apache.staging.https". is that the correct one?
> >
> > On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh <
> cohei...@apache.org
> > > wrote:
> >
> >> Have you got a "apache.releases.https" server defined in your maven
> >> settings.xml, with a corresponding username + password?
> >>
> >> Colm.
> >>
> >> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
> >> kkal...@cloudera.com> wrote:
> >>
> >> > I'm observing error while deploying the artifacts in maven repository.
> >> > Looks like I don't have permission to do it.
> >> >
> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> >> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project
> sentry:
> >> > > Failed to deploy artifacts: Could not transfer artifact
> >> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> >> > > https://repository.apache.org/service/local/staging/deploy/maven2):
> >> > > Failed to transfer file: https://repository.apache.org/
> >> > > service/local/staging/deploy/maven2/org/apache/sentry/
> >> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> >> > > *Unauthorized*. -> [Help 1]
> >> > >
> >> >
> >> >
> >> > Does any one know if I need some permissions to deploy?
> >> >
> >> > -Kalyan
> >> >
> >> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> >> > kkal...@cloudera.com> wrote:
> >> >
> >> > > Sure, I will change the branch to sentry-2.0
> >> > >
> >> > > Thanks,
> >> > > Kalyan
> >> > >
> >> > > -Kalyan
> >> > >
> >> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
> >> sergio.p...@cloudera.com>
> >> > > wrote:
> >> > >
> >> > >> That's old Kalyan. Why do you propose bringing back the old
> approach?
> >> > The
> >> > >> new approach is used by other Apache components where bugfix
> releases
> >> > are
> >> > >> only tags. This reduces the release process and steps of bugfix
> >> > releases.
> >> > >>
> >> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> >> > >> kkal...@cloudera.com> wrote:
> >> > >>
> >> > >> > Sergio,
> >> > >> >
> >> > >> > If you look at all the previous branches they are followed
> >> convention
> >> > >> > sentry-major.minor.patch. I tried to be in-line with them.
> >> > >> >
> >> > >> > -Kalyan
> >> > >> >
> >> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> >> > sergio.p...@cloudera.com>
> >> > >> > wrote:
> >> > >> >
> >> > >> > > Great, thanks Kalyan.
> >> > >> > >
> >> > >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests
> >> (git
> >> > >> > > checkout -b branch-1.8). It is better to name a branch this way
> >> so
> >> > we
> >> > >> can
> >> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> >> > >> > >
> >> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> >> > >> > > kkal...@cloudera.com> wrote:
> >> > >> > >
> >> > >> > > > I've just created new release branch for upcoming 2.0.0
> >> release.
> >> > >> Please
> >> > >> > > > continue committing to master branch as usual.
> >> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >> > >> > > >
> >> > >> > > > -Kalyan
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Colm O hEigeartaigh
> >>
> >> Talend Community Coder
> >> http://coders.talend.com
> >>
> >
> >
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Re: New release branch 2.0.0

[Colm O hEigeartaigh]

Hmm I'm not sure if that's correct, it should look more like:


  


   apache.releases.https
   coheigea
   ...



   apache.staging.https
   coheigea
   ...

  


On Tue, Nov 28, 2017 at 5:02 PM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> Colm,
>
> This the the complete content of my settings.xml.
>>
>> 
>>
>>   apache.staging.https
>>
>>   kalyan
>>
>>   *
>>
>>apache.releases.https
>>
>>   kalyan
>>
>>   *
>>
>>  
>>
>>
>
> I'm running below command.
>
>> mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts
>
>
> I still observe the same issue.
>
> -Kalyan
>
> On Tue, Nov 28, 2017 at 10:46 AM, Colm O hEigeartaigh  > wrote:
>
>> I think it should be "apache.releases.https" based on the error message
>> below. I have both in my local settings.xml, so you could try adding both
>> in!
>>
>> Colm.
>>
>> On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
>> wrote:
>>
>> > I have the same issue.
>> >
>> > Colm, the wiki mentioned "apache.staging.https". is that the correct
>> one?
>> >
>> > On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh <
>> cohei...@apache.org
>> > > wrote:
>> >
>> >> Have you got a "apache.releases.https" server defined in your maven
>> >> settings.xml, with a corresponding username + password?
>> >>
>> >> Colm.
>> >>
>> >> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
>> >> kkal...@cloudera.com> wrote:
>> >>
>> >> > I'm observing error while deploying the artifacts in maven
>> repository.
>> >> > Looks like I don't have permission to do it.
>> >> >
>> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
>> >> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project
>> sentry:
>> >> > > Failed to deploy artifacts: Could not transfer artifact
>> >> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
>> >> > > https://repository.apache.org/service/local/staging/deploy/maven2
>> ):
>> >> > > Failed to transfer file: https://repository.apache.org/
>> >> > > service/local/staging/deploy/maven2/org/apache/sentry/
>> >> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
>> >> > > *Unauthorized*. -> [Help 1]
>> >> > >
>> >> >
>> >> >
>> >> > Does any one know if I need some permissions to deploy?
>> >> >
>> >> > -Kalyan
>> >> >
>> >> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
>> >> > kkal...@cloudera.com> wrote:
>> >> >
>> >> > > Sure, I will change the branch to sentry-2.0
>> >> > >
>> >> > > Thanks,
>> >> > > Kalyan
>> >> > >
>> >> > > -Kalyan
>> >> > >
>> >> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
>> >> sergio.p...@cloudera.com>
>> >> > > wrote:
>> >> > >
>> >> > >> That's old Kalyan. Why do you propose bringing back the old
>> approach?
>> >> > The
>> >> > >> new approach is used by other Apache components where bugfix
>> releases
>> >> > are
>> >> > >> only tags. This reduces the release process and steps of bugfix
>> >> > releases.
>> >> > >>
>> >> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
>> >> > >> kkal...@cloudera.com> wrote:
>> >> > >>
>> >> > >> > Sergio,
>> >> > >> >
>> >> > >> > If you look at all the previous branches they are followed
>> >> convention
>> >> > >> > sentry-major.minor.patch. I tried to be in-line with them.
>> >> > >> >
>> >> > >> > -Kalyan
>> >> > >> >
>> >> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
>> >> > sergio.p...@cloudera.com>
>> >> > >> > wrote:
>> >> > >> >
>> >> > >> > > Great, thanks Kalyan.
>> >> > >> > >
>> >> > >> > > Btw, the branch should be named branch-2.0 as the Wiki
>> suggests
>> >> (git
>> >> > >> > > checkout -b branch-1.8). It is better to name a branch this
>> way
>> >> so
>> >> > we
>> >> > >> can
>> >> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
>> >> > >> > >
>> >> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
>> >> > >> > > kkal...@cloudera.com> wrote:
>> >> > >> > >
>> >> > >> > > > I've just created new release branch for upcoming 2.0.0
>> >> release.
>> >> > >> Please
>> >> > >> > > > continue committing to master branch as usual.
>> >> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
>> >> > >> > > >
>> >> > >> > > > -Kalyan
>> >> > >> > > >
>> >> > >> > >
>> >> > >> >
>> >> > >>
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Colm O hEigeartaigh
>> >>
>> >> Talend Community Coder
>> >> http://coders.talend.com
>> >>
>> >
>> >
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: New release branch 2.0.0

[Kalyan Kumar Kalvagadda]

Colm,

that is the issue. I will update the wiki accordingly.

-Kalyan

On Tue, Nov 28, 2017 at 11:11 AM, Colm O hEigeartaigh 
wrote:

> Hmm I'm not sure if that's correct, it should look more like:
>
> 
>   
>
> 
>apache.releases.https
>coheigea
>...
> 
>
> 
>apache.staging.https
>coheigea
>...
> 
>   
> 
>
> On Tue, Nov 28, 2017 at 5:02 PM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > Colm,
> >
> > This the the complete content of my settings.xml.
> >>
> >> 
> >>
> >>   apache.staging.https
> >>
> >>   kalyan
> >>
> >>   *
> >>
> >>apache.releases.https
> >>
> >>   kalyan
> >>
> >>   *
> >>
> >>  
> >>
> >>
> >
> > I'm running below command.
> >
> >> mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts
> >
> >
> > I still observe the same issue.
> >
> > -Kalyan
> >
> > On Tue, Nov 28, 2017 at 10:46 AM, Colm O hEigeartaigh <
> cohei...@apache.org
> > > wrote:
> >
> >> I think it should be "apache.releases.https" based on the error message
> >> below. I have both in my local settings.xml, so you could try adding
> both
> >> in!
> >>
> >> Colm.
> >>
> >> On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
> >> wrote:
> >>
> >> > I have the same issue.
> >> >
> >> > Colm, the wiki mentioned "apache.staging.https". is that the correct
> >> one?
> >> >
> >> > On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh <
> >> cohei...@apache.org
> >> > > wrote:
> >> >
> >> >> Have you got a "apache.releases.https" server defined in your maven
> >> >> settings.xml, with a corresponding username + password?
> >> >>
> >> >> Colm.
> >> >>
> >> >> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
> >> >> kkal...@cloudera.com> wrote:
> >> >>
> >> >> > I'm observing error while deploying the artifacts in maven
> >> repository.
> >> >> > Looks like I don't have permission to do it.
> >> >> >
> >> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> >> >> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project
> >> sentry:
> >> >> > > Failed to deploy artifacts: Could not transfer artifact
> >> >> > > org.apache.sentry:sentry:pom:2.0.0 from/to
> apache.releases.https (
> >> >> > > https://repository.apache.org/service/local/staging/deploy/
> maven2
> >> ):
> >> >> > > Failed to transfer file: https://repository.apache.org/
> >> >> > > service/local/staging/deploy/maven2/org/apache/sentry/
> >> >> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> >> >> > > *Unauthorized*. -> [Help 1]
> >> >> > >
> >> >> >
> >> >> >
> >> >> > Does any one know if I need some permissions to deploy?
> >> >> >
> >> >> > -Kalyan
> >> >> >
> >> >> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> >> >> > kkal...@cloudera.com> wrote:
> >> >> >
> >> >> > > Sure, I will change the branch to sentry-2.0
> >> >> > >
> >> >> > > Thanks,
> >> >> > > Kalyan
> >> >> > >
> >> >> > > -Kalyan
> >> >> > >
> >> >> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
> >> >> sergio.p...@cloudera.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > >> That's old Kalyan. Why do you propose bringing back the old
> >> approach?
> >> >> > The
> >> >> > >> new approach is used by other Apache components where bugfix
> >> releases
> >> >> > are
> >> >> > >> only tags. This reduces the release process and steps of bugfix
> >> >> > releases.
> >> >> > >>
> >> >> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> >> >> > >> kkal...@cloudera.com> wrote:
> >> >> > >>
> >> >> > >> > Sergio,
> >> >> > >> >
> >> >> > >> > If you look at all the previous branches they are followed
> >> >> convention
> >> >> > >> > sentry-major.minor.patch. I tried to be in-line with them.
> >> >> > >> >
> >> >> > >> > -Kalyan
> >> >> > >> >
> >> >> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> >> >> > sergio.p...@cloudera.com>
> >> >> > >> > wrote:
> >> >> > >> >
> >> >> > >> > > Great, thanks Kalyan.
> >> >> > >> > >
> >> >> > >> > > Btw, the branch should be named branch-2.0 as the Wiki
> >> suggests
> >> >> (git
> >> >> > >> > > checkout -b branch-1.8). It is better to name a branch this
> >> way
> >> >> so
> >> >> > we
> >> >> > >> can
> >> >> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> >> >> > >> > >
> >> >> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> >> >> > >> > > kkal...@cloudera.com> wrote:
> >> >> > >> > >
> >> >> > >> > > > I've just created new release branch for upcoming 2.0.0
> >> >> release.
> >> >> > >> Please
> >> >> > >> > > > continue committing to master branch as usual.
> >> >> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >> >> > >> > > >
> >> >> > >> > > > -Kalyan
> >> >> > >> > > >
> >> >> > >> > >
> >> >> > >> >
> >> >> > >>
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Colm O hEigeartaigh
> >> >>
> >> >> Talend Community Coder
> >> >> http://coders.talend.com
> >> >>
> >> >
> >> >
> >

2.0 release and SENTRY-1812

[Alexander Kolbasov]

Colm, do you plan to include SENTRY-1812 in 2.0 release?

Re: 2.0 release and SENTRY-1812

[Colm O hEigeartaigh]

Yes, it's already merged and the Jira is resolved.

Colm.

On 28 Nov 2017 7:04 p.m., "Alexander Kolbasov"  wrote:

Colm, do you plan to include SENTRY-1812 in 2.0 release?

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

[Vadim Spector via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63596/#review192068
---




sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
Line 2514 (original), 2513 (patched)


So, what are our final assumptions about leading and trailing hashes in 
hdfs paths at the point of adding them to Sentry store? Do we assume they only 
have leading slashes? Can they be multiple slashes or single-only? What about 
trailing slashes - none, single-only, multiple ok?

I start thinking that sentry store should be taking hdfs paths with "bad" 
slashes and canoinicalize them internally. I like the idea of a contract 
between Sentry components in regards to hdfs paths; we keep talking about, but 
the truth is contracts can be inadvertantly broken by code changes. 
Canonicalizing paths seems like a cheap operation, so I think that Sentry store 
should be fine accepting non-canonicalized paths - in fact, we should do just 
that and test the resuts by passing non-canonicalized paths and make sure 
canonicalization happened.

Would like others to weigh in.


- Vadim Spector


On Nov. 27, 2017, 6:03 p.m., Arjun Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63596/
> ---
> 
> (Updated Nov. 27, 2017, 6:03 p.m.)
> 
> 
> Review request for sentry, Alexander Kolbasov, kalyan kumar kalvagadda, Na 
> Li, Sergio Pena, and Vadim Spector.
> 
> 
> Repository: sentry
> 
> 
> Description
> ---
> 
> The old retrieveFullPathsImage() method in SentryStore is no longer used by 
> actual code (retrieveFullPathsImageUpdate(final String[] prefixes) is used 
> instead. It was preserved because it is used by test which now doesn't make 
> much sense.
> 
> 
> Diffs
> -
> 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestImageRetriever.java
>  b355630e7 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestSentryHDFSServiceProcessor.java
>  f09d1b228 
>   
> sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/SentryStore.java
>  f32a745ed 
>   
> sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
>  24b11f724 
> 
> 
> Diff: https://reviews.apache.org/r/63596/diff/2/
> 
> 
> Testing
> ---
> 
> mvn -f sentry-provider/sentry-provider-db/pom.xml test -Dtest=TestSentryStore
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestSentryHDFSServiceProcessor
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestImageRetriever.java
> 
> 
> Thanks,
> 
> Arjun Mishra
> 
>

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

[Vadim Spector via Review Board]

> On Nov. 28, 2017, 10:16 p.m., Vadim Spector wrote:
> > sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
> > Line 2514 (original), 2513 (patched)
> > 
> >
> > So, what are our final assumptions about leading and trailing hashes in 
> > hdfs paths at the point of adding them to Sentry store? Do we assume they 
> > only have leading slashes? Can they be multiple slashes or single-only? 
> > What about trailing slashes - none, single-only, multiple ok?
> > 
> > I start thinking that sentry store should be taking hdfs paths with 
> > "bad" slashes and canoinicalize them internally. I like the idea of a 
> > contract between Sentry components in regards to hdfs paths; we keep 
> > talking about, but the truth is contracts can be inadvertantly broken by 
> > code changes. Canonicalizing paths seems like a cheap operation, so I think 
> > that Sentry store should be fine accepting non-canonicalized paths - in 
> > fact, we should do just that and test the resuts by passing 
> > non-canonicalized paths and make sure canonicalization happened.
> > 
> > Would like others to weigh in.

No matter what we decide, should probably document those assuimptions in the 
test code, if only in couple of sentences.


- Vadim


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63596/#review192068
---


On Nov. 27, 2017, 6:03 p.m., Arjun Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63596/
> ---
> 
> (Updated Nov. 27, 2017, 6:03 p.m.)
> 
> 
> Review request for sentry, Alexander Kolbasov, kalyan kumar kalvagadda, Na 
> Li, Sergio Pena, and Vadim Spector.
> 
> 
> Repository: sentry
> 
> 
> Description
> ---
> 
> The old retrieveFullPathsImage() method in SentryStore is no longer used by 
> actual code (retrieveFullPathsImageUpdate(final String[] prefixes) is used 
> instead. It was preserved because it is used by test which now doesn't make 
> much sense.
> 
> 
> Diffs
> -
> 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestImageRetriever.java
>  b355630e7 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestSentryHDFSServiceProcessor.java
>  f09d1b228 
>   
> sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/SentryStore.java
>  f32a745ed 
>   
> sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
>  24b11f724 
> 
> 
> Diff: https://reviews.apache.org/r/63596/diff/2/
> 
> 
> Testing
> ---
> 
> mvn -f sentry-provider/sentry-provider-db/pom.xml test -Dtest=TestSentryStore
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestSentryHDFSServiceProcessor
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestImageRetriever.java
> 
> 
> Thanks,
> 
> Arjun Mishra
> 
>

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

[Arjun Mishra via Review Board]

> On Nov. 28, 2017, 10:16 p.m., Vadim Spector wrote:
> > sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
> > Line 2514 (original), 2513 (patched)
> > 
> >
> > So, what are our final assumptions about leading and trailing hashes in 
> > hdfs paths at the point of adding them to Sentry store? Do we assume they 
> > only have leading slashes? Can they be multiple slashes or single-only? 
> > What about trailing slashes - none, single-only, multiple ok?
> > 
> > I start thinking that sentry store should be taking hdfs paths with 
> > "bad" slashes and canoinicalize them internally. I like the idea of a 
> > contract between Sentry components in regards to hdfs paths; we keep 
> > talking about, but the truth is contracts can be inadvertantly broken by 
> > code changes. Canonicalizing paths seems like a cheap operation, so I think 
> > that Sentry store should be fine accepting non-canonicalized paths - in 
> > fact, we should do just that and test the resuts by passing 
> > non-canonicalized paths and make sure canonicalization happened.
> > 
> > Would like others to weigh in.
> 
> Vadim Spector wrote:
> No matter what we decide, should probably document those assuimptions in 
> the test code, if only in couple of sentences.

Vadim, the newer version doesn't have the specific line you have commented 
against. In the new version all the test cases are unchanged with respect to 
the inputs that are being fed


- Arjun


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63596/#review192068
---


On Nov. 27, 2017, 6:03 p.m., Arjun Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63596/
> ---
> 
> (Updated Nov. 27, 2017, 6:03 p.m.)
> 
> 
> Review request for sentry, Alexander Kolbasov, kalyan kumar kalvagadda, Na 
> Li, Sergio Pena, and Vadim Spector.
> 
> 
> Repository: sentry
> 
> 
> Description
> ---
> 
> The old retrieveFullPathsImage() method in SentryStore is no longer used by 
> actual code (retrieveFullPathsImageUpdate(final String[] prefixes) is used 
> instead. It was preserved because it is used by test which now doesn't make 
> much sense.
> 
> 
> Diffs
> -
> 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestImageRetriever.java
>  b355630e7 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestSentryHDFSServiceProcessor.java
>  f09d1b228 
>   
> sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/SentryStore.java
>  f32a745ed 
>   
> sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
>  24b11f724 
> 
> 
> Diff: https://reviews.apache.org/r/63596/diff/2/
> 
> 
> Testing
> ---
> 
> mvn -f sentry-provider/sentry-provider-db/pom.xml test -Dtest=TestSentryStore
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestSentryHDFSServiceProcessor
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestImageRetriever.java
> 
> 
> Thanks,
> 
> Arjun Mishra
> 
>

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

[Vadim Spector via Review Board]

> On Nov. 28, 2017, 10:16 p.m., Vadim Spector wrote:
> > sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
> > Line 2514 (original), 2513 (patched)
> > 
> >
> > So, what are our final assumptions about leading and trailing hashes in 
> > hdfs paths at the point of adding them to Sentry store? Do we assume they 
> > only have leading slashes? Can they be multiple slashes or single-only? 
> > What about trailing slashes - none, single-only, multiple ok?
> > 
> > I start thinking that sentry store should be taking hdfs paths with 
> > "bad" slashes and canoinicalize them internally. I like the idea of a 
> > contract between Sentry components in regards to hdfs paths; we keep 
> > talking about, but the truth is contracts can be inadvertantly broken by 
> > code changes. Canonicalizing paths seems like a cheap operation, so I think 
> > that Sentry store should be fine accepting non-canonicalized paths - in 
> > fact, we should do just that and test the resuts by passing 
> > non-canonicalized paths and make sure canonicalization happened.
> > 
> > Would like others to weigh in.
> 
> Vadim Spector wrote:
> No matter what we decide, should probably document those assuimptions in 
> the test code, if only in couple of sentences.
> 
> Arjun Mishra wrote:
> Vadim, the newer version doesn't have the specific line you have 
> commented against. In the new version all the test cases are unchanged with 
> respect to the inputs that are being fed

Does not really matter, imo. The point is, we switch to another API, and change 
tests accordingly. It may be a good time to clearly state our assumptions (and 
probably even change them), to avoid future problems. We know how hard it is to 
debug issues involving incorrect hdfs path parsing; cheaper to harden our code 
right now, imo.


- Vadim


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63596/#review192068
---


On Nov. 27, 2017, 6:03 p.m., Arjun Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63596/
> ---
> 
> (Updated Nov. 27, 2017, 6:03 p.m.)
> 
> 
> Review request for sentry, Alexander Kolbasov, kalyan kumar kalvagadda, Na 
> Li, Sergio Pena, and Vadim Spector.
> 
> 
> Repository: sentry
> 
> 
> Description
> ---
> 
> The old retrieveFullPathsImage() method in SentryStore is no longer used by 
> actual code (retrieveFullPathsImageUpdate(final String[] prefixes) is used 
> instead. It was preserved because it is used by test which now doesn't make 
> much sense.
> 
> 
> Diffs
> -
> 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestImageRetriever.java
>  b355630e7 
>   
> sentry-hdfs/sentry-hdfs-service/src/test/java/org/apache/sentry/hdfs/TestSentryHDFSServiceProcessor.java
>  f09d1b228 
>   
> sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/SentryStore.java
>  f32a745ed 
>   
> sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java
>  24b11f724 
> 
> 
> Diff: https://reviews.apache.org/r/63596/diff/2/
> 
> 
> Testing
> ---
> 
> mvn -f sentry-provider/sentry-provider-db/pom.xml test -Dtest=TestSentryStore
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestSentryHDFSServiceProcessor
> mvn -f sentry-hdfs/sentry-hdfs-service/pom.xml test 
> -Dtest=TestImageRetriever.java
> 
> 
> Thanks,
> 
> Arjun Mishra
> 
>

[VOTE] Release Sentry version 2.0.0

[Kalyan Kumar Kalvagadda]

This is the release of Apache Sentry, version 2.0.0.

It fixes the following issues:
*https://issues.apache.org/jira/projects/SENTRY/versions/12341081
*

Source and bin files :
*http://home.apache.org/~kalyan/apache-sentry-2.0.0-src-rc-1/
*

Maven artifacts are available
here:https://repository.apache.org/content/repositories/orgapachesentry-1005/


Tag to be voted on
*https://git-wip-us.apache.org/repos/asf/sentry/?p=sentry.git;a=tag;h=refs/tags/release-2.0.0
*

Sentry's KEYS containing the PGP key we used to sign the release:
http://www.apache.org/dist/sentry/KEYS

 we are voting on the source:tag=release-2.0.0, SHA=
18fe7c596fa1ffad3e656a42d534ac190876b642
 (You can get the hash of the tag by doing "git rev-list release-1.8.0 |
head -n 1" )

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Kalyan