[jira] [Updated] (PHOENIX-7079) Omid 1.1.0 update breaks HBase 2.1 build because of netty version conflict

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-7079:
-
Description: 
{noformat}
[ERROR] Tests run: 43, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 
206.097 s <<< FAILURE! - in org.apache.phoenix.end2end.CreateTableIT
[ERROR] 
org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
  Time elapsed: 0.266 s  <<< ERROR!
com.google.inject.ProvisionException: 
Unable to provision, see the following errors:1) Error injecting constructor, 
java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
{noformat}
{noformat}
Caused by: java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
    at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94)
    at 
org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
    at 
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
    at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
    at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
    at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
 {noformat}

  was:
 
{noformat}
Caused by: java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
    at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94)
    at 
org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
    at 
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
    at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
    at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
    at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
 {noformat}


> Omid 1.1.0 update breaks HBase 2.1 build because of netty version conflict
> --
>
> Key: PHOENIX-7079
> URL: https://issues.apache.org/jira/browse/PHOENIX-7079
> Project: Phoenix
>  Issue Type: New Feature
>  Components: core, omid
>Affects Versions: 5.1.4
>Reporter: Istvan Toth
>Priority: Major
>
> {noformat}
> [ERROR] Tests run: 43, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 
> 206.097 s <<< FAILURE! - in org.apache.phoenix.end2end.CreateTableIT
> [ERROR] 
> org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
>   Time elapsed: 0.266 s  <<< ERROR!
> com.google.inject.ProvisionException: 
> Unable to provision, see the following errors:1) Error injecting constructor, 
> java.lang.NoSuchMethodError: 'void 
> io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
> {noformat}
> {noformat}
> Caused by: java.lang.NoSuchMethodError: 'void 
> io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
>     at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94)
>     at 
> org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
>     at 
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
>     at 
> com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
>     at 
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
>     at 
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
>  {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7079) Omid 1.1.0 update breaks HBase 2.1 build because of netty version conflict

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-7079:
-
Description: 
 
{noformat}
[ERROR] Tests run: 43, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 
206.097 s <<< FAILURE! - in org.apache.phoenix.end2end.CreateTableIT[ERROR] 
org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
  Time elapsed: 0.266 s  <<< ERROR!com.google.inject.ProvisionException: Unable 
to provision, see the following errors:
1) Error injecting constructor, java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
  at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:83)  
at org.apache.omid.tso.TSOMockModule.configure(TSOMockModule.java:51)  while 
locating org.apache.omid.tso.TSOChannelHandler    for parameter 0 at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  while locating 
org.apache.omid.tso.LeaseManagement    for parameter 2 at 
org.apache.omid.tso.PersistenceProcessorHandler.(PersistenceProcessorHandler.java:69)
  while locating org.apache.omid.tso.PersistenceProcessorHandler  at 
org.apache.omid.tso.TSOMockModule.getPersistenceProcessorHandler(TSOMockModule.java:88)
  while locating org.apache.omid.tso.PersistenceProcessorHandler[]    for 
parameter 5 at 
org.apache.omid.tso.PersistenceProcessorImpl.(PersistenceProcessorImpl.java:73)
  while locating org.apache.omid.tso.PersistenceProcessorImpl  at 
org.apache.omid.tso.DisruptorModule.configure(DisruptorModule.java:59) (via 
modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.DisruptorModule)  while locating 
org.apache.omid.tso.PersistenceProcessor    for parameter 2 at 
org.apache.omid.tso.RequestProcessorPersistCT.(RequestProcessorPersistCT.java:40)
  while locating org.apache.omid.tso.RequestProcessorPersistCT  at 
org.apache.omid.tso.DisruptorModule.configure(DisruptorModule.java:60) (via 
modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.DisruptorModule)  while locating 
org.apache.omid.tso.RequestProcessor    for field at 
org.apache.omid.tso.TSOServer.requestProcessor(TSOServer.java:37)  at 
org.apache.omid.tso.TSOServer.class(TSOServer.java:37)  while locating 
org.apache.omid.tso.TSOServerCaused by: java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
 at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94) 
 at 
org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
   at 
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
   at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
{noformat}

  was:
 
{noformat}
ERROR] Tests run: 43, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 206.097 
s <<< FAILURE! - in org.apache.phoenix.end2end.CreateTableIT[ERROR] 
org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
  Time elapsed: 0.266 s  <<< ERROR!com.google.inject.ProvisionException: Unable 
to provision, see the following errors:
1) Error injecting constructor, java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
  at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:83)  
at org.apache.omid.tso.TSOMockModule.configure(TSOMockModule.java:51)  while 
locating org.apache.omid.tso.TSOChannelHandler    for parameter 0 at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  while locating 
org.apache.omid.tso.LeaseManagement    for parameter 2 at 
org.apache.omid.tso.PersistenceProcessorHandler.(PersistenceProcessorHandler.java:69)
  while locating org.apache.omid.tso.PersistenceProcessorHandler  at 

[jira] [Updated] (PHOENIX-7079) Omid 1.1.0 update breaks HBase 2.1 build because of netty version conflict

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-7079:
-
Description: 
 
{noformat}
Caused by: java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
    at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94)
    at 
org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
    at 
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
    at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
    at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
    at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
 {noformat}

  was:
 
{noformat}
[ERROR] Tests run: 43, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 
206.097 s <<< FAILURE! - in org.apache.phoenix.end2end.CreateTableIT[ERROR] 
org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
  Time elapsed: 0.266 s  <<< ERROR!com.google.inject.ProvisionException: Unable 
to provision, see the following errors:
1) Error injecting constructor, java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
  at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:83)  
at org.apache.omid.tso.TSOMockModule.configure(TSOMockModule.java:51)  while 
locating org.apache.omid.tso.TSOChannelHandler    for parameter 0 at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  while locating 
org.apache.omid.tso.LeaseManagement    for parameter 2 at 
org.apache.omid.tso.PersistenceProcessorHandler.(PersistenceProcessorHandler.java:69)
  while locating org.apache.omid.tso.PersistenceProcessorHandler  at 
org.apache.omid.tso.TSOMockModule.getPersistenceProcessorHandler(TSOMockModule.java:88)
  while locating org.apache.omid.tso.PersistenceProcessorHandler[]    for 
parameter 5 at 
org.apache.omid.tso.PersistenceProcessorImpl.(PersistenceProcessorImpl.java:73)
  while locating org.apache.omid.tso.PersistenceProcessorImpl  at 
org.apache.omid.tso.DisruptorModule.configure(DisruptorModule.java:59) (via 
modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.DisruptorModule)  while locating 
org.apache.omid.tso.PersistenceProcessor    for parameter 2 at 
org.apache.omid.tso.RequestProcessorPersistCT.(RequestProcessorPersistCT.java:40)
  while locating org.apache.omid.tso.RequestProcessorPersistCT  at 
org.apache.omid.tso.DisruptorModule.configure(DisruptorModule.java:60) (via 
modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.DisruptorModule)  while locating 
org.apache.omid.tso.RequestProcessor    for field at 
org.apache.omid.tso.TSOServer.requestProcessor(TSOServer.java:37)  at 
org.apache.omid.tso.TSOServer.class(TSOServer.java:37)  while locating 
org.apache.omid.tso.TSOServerCaused by: java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
 at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94) 
 at 
org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
   at 
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
   at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
{noformat}


> Omid 1.1.0 update breaks HBase 2.1 build because of netty version conflict
> --
>
> Key: PHOENIX-7079
> URL: https://issues.apache.org/jira/browse/PHOENIX-7079
> Project: Phoenix
>  Issue Type: New Feature
>  Components: core, omid
>Affects Versions: 5.1.4
>Reporter: Istvan Toth
>Priority: Major
>
>  
> {noformat}
> Caused by: java.lang.NoSuchMethodError: 'void 
> io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
>     at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94)
>     at 
> org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
>     at 
> 

[jira] [Created] (PHOENIX-7079) Omid 1.1.0 update breaks HBase 2.1 build because of netty version conflict

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7079:


 Summary: Omid 1.1.0 update breaks HBase 2.1 build because of netty 
version conflict
 Key: PHOENIX-7079
 URL: https://issues.apache.org/jira/browse/PHOENIX-7079
 Project: Phoenix
  Issue Type: New Feature
  Components: core, omid
Affects Versions: 5.1.4
Reporter: Istvan Toth


 
{noformat}
ERROR] Tests run: 43, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 206.097 
s <<< FAILURE! - in org.apache.phoenix.end2end.CreateTableIT[ERROR] 
org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
  Time elapsed: 0.266 s  <<< ERROR!com.google.inject.ProvisionException: Unable 
to provision, see the following errors:
1) Error injecting constructor, java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
  at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:83)  
at org.apache.omid.tso.TSOMockModule.configure(TSOMockModule.java:51)  while 
locating org.apache.omid.tso.TSOChannelHandler    for parameter 0 at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  at 
org.apache.omid.tso.VoidLeaseManagementModule.provideLeaseManager(VoidLeaseManagementModule.java:51)
 (via modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.VoidLeaseManagementModule)  while locating 
org.apache.omid.tso.LeaseManagement    for parameter 2 at 
org.apache.omid.tso.PersistenceProcessorHandler.(PersistenceProcessorHandler.java:69)
  while locating org.apache.omid.tso.PersistenceProcessorHandler  at 
org.apache.omid.tso.TSOMockModule.getPersistenceProcessorHandler(TSOMockModule.java:88)
  while locating org.apache.omid.tso.PersistenceProcessorHandler[]    for 
parameter 5 at 
org.apache.omid.tso.PersistenceProcessorImpl.(PersistenceProcessorImpl.java:73)
  while locating org.apache.omid.tso.PersistenceProcessorImpl  at 
org.apache.omid.tso.DisruptorModule.configure(DisruptorModule.java:59) (via 
modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.DisruptorModule)  while locating 
org.apache.omid.tso.PersistenceProcessor    for parameter 2 at 
org.apache.omid.tso.RequestProcessorPersistCT.(RequestProcessorPersistCT.java:40)
  while locating org.apache.omid.tso.RequestProcessorPersistCT  at 
org.apache.omid.tso.DisruptorModule.configure(DisruptorModule.java:60) (via 
modules: org.apache.omid.tso.TSOMockModule -> 
org.apache.omid.tso.DisruptorModule)  while locating 
org.apache.omid.tso.RequestProcessor    for field at 
org.apache.omid.tso.TSOServer.requestProcessor(TSOServer.java:37)  at 
org.apache.omid.tso.TSOServer.class(TSOServer.java:37)  while locating 
org.apache.omid.tso.TSOServerCaused by: java.lang.NoSuchMethodError: 'void 
io.netty.channel.nio.NioEventLoopGroup.(java.util.concurrent.ThreadFactory)'
 at org.apache.omid.tso.TSOChannelHandler.(TSOChannelHandler.java:94) 
 at 
org.apache.omid.tso.TSOChannelHandler$$FastClassByGuice$$1ec2795a.newInstance()
   at 
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
   at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
{noformat}
 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Phoenix 5.1.4 release

[rajeshb...@apache.org]

Sure Istvan.

We are setting up security scans and fix all possible vulnerabilities ASAP.

Nihal Jain from our team looking into it.

Thanks,
Rajeshbabu.


On Thu, Oct 19, 2023, 9:35 AM Istvan Toth 
wrote:

> Regarding the guava update:
> Since we're no longer supporting Java 7, we should switch to standard guava
> in phoenix-thirdparty.
>
> The Omid repo also has several CVE related patches.
> It would be nice to release Omid 1.1.1 before Phoenix 5.1.4 to make use of
> them.
>
> Istvan
>
> On Thu, Oct 19, 2023 at 4:35 AM rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > Sure Istvan, am fine not delete old versions.
> >
> > We need to release phoenix-thirdparty fixing the guava vulnerability and
> > make use here would be better.
> >
> > I would like to release it this weekend. If required will start another
> > discussion thread or start release.
> >
> > @Visa we are trying to productionize the Phoenix with ACID compliance. We
> > are in the early stages.
> >
> >
> >
> > On Wed, Oct 18, 2023, 11:01 PM Viraj Jasani  wrote:
> >
> > > Sounds good Istvan, let’s keep the versions.
> > >
> > > And thank you so much for fixing broken compilation for 2.1 and 2.2
> > > versions:
> > > https://github.com/apache/phoenix/pull/1714
> > >
> > >
> > > On Tue, Oct 17, 2023 at 11:05 PM Istvan Toth
>  > >
> > > wrote:
> > >
> > > > I very much agree on the release.
> > > >
> > > > I don't remember why we didn't bump the Omid version in 5.1 after it
> > was
> > > > released.
> > > > If it doesn't break anything, then it's a good thing.
> > > >
> > > > I disagree on removing the old HBase version support.
> > > >
> > > > Just as HBase doesn't remove support for old Hadoop versions in new
> > patch
> > > > (or even minor) releases,
> > > > I think it would be much kinder to our users not to force them to
> > upgrade
> > > > HBase, when it really doesn't cost us
> > > > much to maintain support for the old versions. (Even if the build
> with
> > > 2.1
> > > > and 2.2 is broken now)
> > > >
> > > > I think that we should make an effort to increase Phoenix adoption
> > beyond
> > > > SFDC and the CLDR customer base.
> > > > Making life easier for users of the Apache releases by not forcing an
> > > HBase
> > > > upgrade is a step in that direction.
> > > > Regular releases are also something that projects the image of a
> > healthy
> > > > project.
> > > >
> > > > Disclaimer: CLDR maintains an LTS release with Phoenix 5.1 and HBase
> > 2.2,
> > > > so it would make life a bit harder for us, too.
> > > >
> > > > Istvan
> > > >
> > > > On Wed, Oct 18, 2023 at 6:57 AM Viraj Jasani 
> > wrote:
> > > >
> > > > > Thank you for the response, Rajeshbabu.
> > > > >
> > > > > > Bump up  Omid to 1.1.0
> > > > >
> > > > > Sounds good.
> > > > >
> > > > >
> > > > > > Remove the support of HBase versions <2.3.x
> > > > >
> > > > > Those versions are long EOL'ed so yes perhaps it makes sense to
> drop
> > > > their
> > > > > support, though I am not sure if we need to manage compatibility
> for
> > > the
> > > > > patch release.
> > > > > If we have consensus, it's fine to remove them. No strong opinion
> > > either
> > > > > way but I am slightly inclined to remove the support since they are
> > > > already
> > > > > EOL'ed.
> > > > >
> > > > > 2.3 is also EOL'ed, but we should keep it anyway since it was a
> > stable
> > > > > release line for quite some time and some users might still be
> using
> > > > 2.3.x
> > > > > versions.
> > > > >
> > > > >
> > > > > On Tue, Oct 17, 2023 at 9:38 PM rajeshb...@apache.org <
> > > > > chrajeshbab...@gmail.com> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Would be better to do few things before release.
> > > > > > 1) Bump up  Omid to 1.1.0
> > > > > > 2) Remove the support of HBase versions <2.3.x
> > > > > >
> > > > > > These would just backports . I will do it if it's fine.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > >
> > > > > > On Wed, Oct 18, 2023 at 9:14 AM Viraj Jasani  >
> > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > It's been almost a year since we had the last patch release on
> > the
> > > > 5.1
> > > > > > > release line. As discussed on other threads, 5.2 release can
> > wait a
> > > > > > little
> > > > > > > longer for some of the features that are in progress. In the
> > > > meantime,
> > > > > we
> > > > > > > should also keep the 5.1 release line active.
> > > > > > >
> > > > > > > We have some good contributions on the 5.1 release line. Unless
> > > > anyone
> > > > > > > would like to be the RM for 5.1.4, I would volunteer to start
> the
> > > > > release
> > > > > > > preparation early next week.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > *István Tóth* | Sr. Staff Software Engineer
> > > > *Email*: st...@cloudera.com
> > > > cloudera.com 
> > > > [image: Cloudera] 
> > > > [image: Cloudera on Twitter]  [image:

[jira] [Updated] (PHOENIX-7078) java.lang.NoSuchMethodError in CreateTableIT with HBase 2.1

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-7078:
-
Issue Type: Bug  (was: New Feature)

> java.lang.NoSuchMethodError in CreateTableIT with HBase 2.1
> ---
>
> Key: PHOENIX-7078
> URL: https://issues.apache.org/jira/browse/PHOENIX-7078
> Project: Phoenix
>  Issue Type: Bug
>  Components: core, omid
>Reporter: Istvan Toth
>Priority: Major
>
> Looks like some kind of Guava version issue.
> This is WITHOUT the Omid 1.1.0 update
> When did this break ?
> {noformat}
> [ERROR] 
> org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
>   Time elapsed: 0.064 s  <<< ERROR!
> java.lang.NoSuchMethodError: 'com.google.common.base.Stopwatch 
> com.google.common.base.Stopwatch.createUnstarted()'
>     at 
> com.google.inject.internal.InternalInjectorCreator.(InternalInjectorCreator.java:64)
>     at com.google.inject.Guice.createInjector(Guice.java:87)
>     at com.google.inject.Guice.createInjector(Guice.java:69)
>     at com.google.inject.Guice.createInjector(Guice.java:59)
>     at 
> org.apache.phoenix.transaction.OmidTransactionService.startAndInjectOmidTransactionService(OmidTransactionService.java:72)
> ...{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7078) java.lang.NoSuchMethodError in CreateTableIT with HBase 2.1

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7078:


 Summary: java.lang.NoSuchMethodError in CreateTableIT with HBase 
2.1
 Key: PHOENIX-7078
 URL: https://issues.apache.org/jira/browse/PHOENIX-7078
 Project: Phoenix
  Issue Type: New Feature
  Components: core, omid
Reporter: Istvan Toth


Looks like some kind of Guava version issue.
This is WITHOUT the Omid 1.1.0 update
When did this break ?
{noformat}
[ERROR] 
org.apache.phoenix.end2end.CreateTableIT.testCoprocessorsForTransactionalCreateIndexOnOldImplementation
  Time elapsed: 0.064 s  <<< ERROR!
java.lang.NoSuchMethodError: 'com.google.common.base.Stopwatch 
com.google.common.base.Stopwatch.createUnstarted()'
    at 
com.google.inject.internal.InternalInjectorCreator.(InternalInjectorCreator.java:64)
    at com.google.inject.Guice.createInjector(Guice.java:87)
    at com.google.inject.Guice.createInjector(Guice.java:69)
    at com.google.inject.Guice.createInjector(Guice.java:59)
    at 
org.apache.phoenix.transaction.OmidTransactionService.startAndInjectOmidTransactionService(OmidTransactionService.java:72)
...{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-251) Bump license-maven-plugin to latest version

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1012#comment-1012
 ] 

ASF GitHub Bot commented on OMID-251:
-

chrajeshbabu merged PR #142:
URL: https://github.com/apache/phoenix-omid/pull/142




> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 1.1.1
>
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to 
> {{{}2.11{}}}, which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned plugin to latest 
> version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log, for reference, of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with version:
>  * {{{}2.11{}}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{{}4.3{}}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7077) Fix flaky PermissionNSEnabledWithCustomAccessControllerIT.testSystemTablePermissions test

[Rajeshbabu Chintaguntla (Jira)]

Rajeshbabu Chintaguntla created PHOENIX-7077:


 Summary: Fix flaky 
PermissionNSEnabledWithCustomAccessControllerIT.testSystemTablePermissions test
 Key: PHOENIX-7077
 URL: https://issues.apache.org/jira/browse/PHOENIX-7077
 Project: Phoenix
  Issue Type: Bug
Reporter: Rajeshbabu Chintaguntla
Assignee: Rajeshbabu Chintaguntla


iN one of the 5.1 PR builds following test case failing randomly, Identify the 
root cause and fix it.

{noformat}

[ERROR] Tests run: 15, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
486.171 s <<< FAILURE! - in 
org.apache.phoenix.end2end.PermissionNSEnabledWithCustomAccessControllerIT 
[ERROR] 
org.apache.phoenix.end2end.PermissionNSEnabledWithCustomAccessControllerIT.testSystemTablePermissions
 Time elapsed: 4.767 s <<< ERROR! 
java.lang.reflect.UndeclaredThrowableException at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1747)
 at org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:325) 
at 
org.apache.phoenix.end2end.BasePermissionsIT.verifyAllowed(BasePermissionsIT.java:914)
 at 
org.apache.phoenix.end2end.BasePermissionsIT.verifyAllowed(BasePermissionsIT.java:907)
 at 
org.apache.phoenix.end2end.BasePermissionsIT.testSystemTablePermissions(BasePermissionsIT.java:1040)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498) at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) 
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
 at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) 
at org.apache.phoenix.SystemExitRule$1.evaluate(SystemExitRule.java:40) at 
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at 
org.junit.rules.RunRules.evaluate(RunRules.java:20) at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413) at 
org.junit.runners.Suite.runChild(Suite.java:128) at 
org.junit.runners.Suite.runChild(Suite.java:27) at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413) at 
org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:49) at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:120)
 at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:95)
 at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
 at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:69)
 at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:146)
 at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
 at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162) at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507) at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495) 
Caused by: org.apache.phoenix.exception.PhoenixIOException: 
org.apache.hadoop.hbase.security.AccessDeniedException: Insufficient 
permissions (user=regularUser1_N000125, scope=SYSTEM, 
params=[namespace=SYSTEM,],action=ADMIN) at 

[jira] [Resolved] (OMID-251) Bump license-maven-plugin to latest version

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved OMID-251.
--
Fix Version/s: 1.1.1
   Resolution: Fixed

Committed to master.
Thanks for the patch [~nihaljain] .

> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 1.1.1
>
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to 
> {{{}2.11{}}}, which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned plugin to latest 
> version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log, for reference, of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with version:
>  * {{{}2.11{}}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{{}4.3{}}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (PHOENIX-2873) Phoenix : Update protobuf-java and guava version

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved PHOENIX-2873.
--
Resolution: Duplicate

> Phoenix : Update protobuf-java and guava version
> 
>
> Key: PHOENIX-2873
> URL: https://issues.apache.org/jira/browse/PHOENIX-2873
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Naveen
>Priority: Critical
>
> Hi,
> My application does have dependency on protobuf-java.version 3.0.0-beta-1 and 
> guava.version 19.0, which also planning to use phoenix.
> Phoenix latest version uses older protobuf-java and guava version ( 
> protobuf-java.version 2.5 and guava.version 13.0.1 ). Made changes in phoenix 
> code base to work with latest version.
> Please suggest how can i get code review done, and contribute same in phoenix 
> code base ?
> Thanks & Regards,
> Naveen Nahata



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (OMID-251) Bump license-maven-plugin to latest version

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth reassigned OMID-251:


Assignee: Nihal Jain

> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to 
> {{{}2.11{}}}, which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned plugin to latest 
> version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log, for reference, of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with version:
>  * {{{}2.11{}}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{{}4.3{}}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Phoenix 5.1.4 release

[Istvan Toth]

Regarding the guava update:
Since we're no longer supporting Java 7, we should switch to standard guava
in phoenix-thirdparty.

The Omid repo also has several CVE related patches.
It would be nice to release Omid 1.1.1 before Phoenix 5.1.4 to make use of
them.

Istvan

On Thu, Oct 19, 2023 at 4:35 AM rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Sure Istvan, am fine not delete old versions.
>
> We need to release phoenix-thirdparty fixing the guava vulnerability and
> make use here would be better.
>
> I would like to release it this weekend. If required will start another
> discussion thread or start release.
>
> @Visa we are trying to productionize the Phoenix with ACID compliance. We
> are in the early stages.
>
>
>
> On Wed, Oct 18, 2023, 11:01 PM Viraj Jasani  wrote:
>
> > Sounds good Istvan, let’s keep the versions.
> >
> > And thank you so much for fixing broken compilation for 2.1 and 2.2
> > versions:
> > https://github.com/apache/phoenix/pull/1714
> >
> >
> > On Tue, Oct 17, 2023 at 11:05 PM Istvan Toth  >
> > wrote:
> >
> > > I very much agree on the release.
> > >
> > > I don't remember why we didn't bump the Omid version in 5.1 after it
> was
> > > released.
> > > If it doesn't break anything, then it's a good thing.
> > >
> > > I disagree on removing the old HBase version support.
> > >
> > > Just as HBase doesn't remove support for old Hadoop versions in new
> patch
> > > (or even minor) releases,
> > > I think it would be much kinder to our users not to force them to
> upgrade
> > > HBase, when it really doesn't cost us
> > > much to maintain support for the old versions. (Even if the build with
> > 2.1
> > > and 2.2 is broken now)
> > >
> > > I think that we should make an effort to increase Phoenix adoption
> beyond
> > > SFDC and the CLDR customer base.
> > > Making life easier for users of the Apache releases by not forcing an
> > HBase
> > > upgrade is a step in that direction.
> > > Regular releases are also something that projects the image of a
> healthy
> > > project.
> > >
> > > Disclaimer: CLDR maintains an LTS release with Phoenix 5.1 and HBase
> 2.2,
> > > so it would make life a bit harder for us, too.
> > >
> > > Istvan
> > >
> > > On Wed, Oct 18, 2023 at 6:57 AM Viraj Jasani 
> wrote:
> > >
> > > > Thank you for the response, Rajeshbabu.
> > > >
> > > > > Bump up  Omid to 1.1.0
> > > >
> > > > Sounds good.
> > > >
> > > >
> > > > > Remove the support of HBase versions <2.3.x
> > > >
> > > > Those versions are long EOL'ed so yes perhaps it makes sense to drop
> > > their
> > > > support, though I am not sure if we need to manage compatibility for
> > the
> > > > patch release.
> > > > If we have consensus, it's fine to remove them. No strong opinion
> > either
> > > > way but I am slightly inclined to remove the support since they are
> > > already
> > > > EOL'ed.
> > > >
> > > > 2.3 is also EOL'ed, but we should keep it anyway since it was a
> stable
> > > > release line for quite some time and some users might still be using
> > > 2.3.x
> > > > versions.
> > > >
> > > >
> > > > On Tue, Oct 17, 2023 at 9:38 PM rajeshb...@apache.org <
> > > > chrajeshbab...@gmail.com> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Would be better to do few things before release.
> > > > > 1) Bump up  Omid to 1.1.0
> > > > > 2) Remove the support of HBase versions <2.3.x
> > > > >
> > > > > These would just backports . I will do it if it's fine.
> > > > >
> > > > > Thanks,
> > > > >
> > > > >
> > > > > On Wed, Oct 18, 2023 at 9:14 AM Viraj Jasani 
> > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > It's been almost a year since we had the last patch release on
> the
> > > 5.1
> > > > > > release line. As discussed on other threads, 5.2 release can
> wait a
> > > > > little
> > > > > > longer for some of the features that are in progress. In the
> > > meantime,
> > > > we
> > > > > > should also keep the 5.1 release line active.
> > > > > >
> > > > > > We have some good contributions on the 5.1 release line. Unless
> > > anyone
> > > > > > would like to be the RM for 5.1.4, I would volunteer to start the
> > > > release
> > > > > > preparation early next week.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > *István Tóth* | Sr. Staff Software Engineer
> > > *Email*: st...@cloudera.com
> > > cloudera.com 
> > > [image: Cloudera] 
> > > [image: Cloudera on Twitter]  [image:
> > > Cloudera on Facebook]  [image:
> > Cloudera
> > > on LinkedIn] 
> > > --
> > > --
> > >
> >
>


-- 
*István Tóth* | Sr. Staff Software Engineer
*Email*: st...@cloudera.com
cloudera.com 
[image: Cloudera] 
[image: Cloudera on Twitter]  [image:
Cloudera on Facebook] 

[jira] [Commented] (OMID-251) Bump license-maven-plugin to latest version

[Istvan Toth (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776995#comment-17776995
 ] 

Istvan Toth commented on OMID-251:
--

I have added you, [~nihaljain.cs] .

> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to 
> {{{}2.11{}}}, which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned plugin to latest 
> version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log, for reference, of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with version:
>  * {{{}2.11{}}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{{}4.3{}}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Phoenix 5.1.4 release

[rajeshb...@apache.org]

Sure Istvan, am fine not delete old versions.

We need to release phoenix-thirdparty fixing the guava vulnerability and
make use here would be better.

I would like to release it this weekend. If required will start another
discussion thread or start release.

@Visa we are trying to productionize the Phoenix with ACID compliance. We
are in the early stages.



On Wed, Oct 18, 2023, 11:01 PM Viraj Jasani  wrote:

> Sounds good Istvan, let’s keep the versions.
>
> And thank you so much for fixing broken compilation for 2.1 and 2.2
> versions:
> https://github.com/apache/phoenix/pull/1714
>
>
> On Tue, Oct 17, 2023 at 11:05 PM Istvan Toth 
> wrote:
>
> > I very much agree on the release.
> >
> > I don't remember why we didn't bump the Omid version in 5.1 after it was
> > released.
> > If it doesn't break anything, then it's a good thing.
> >
> > I disagree on removing the old HBase version support.
> >
> > Just as HBase doesn't remove support for old Hadoop versions in new patch
> > (or even minor) releases,
> > I think it would be much kinder to our users not to force them to upgrade
> > HBase, when it really doesn't cost us
> > much to maintain support for the old versions. (Even if the build with
> 2.1
> > and 2.2 is broken now)
> >
> > I think that we should make an effort to increase Phoenix adoption beyond
> > SFDC and the CLDR customer base.
> > Making life easier for users of the Apache releases by not forcing an
> HBase
> > upgrade is a step in that direction.
> > Regular releases are also something that projects the image of a healthy
> > project.
> >
> > Disclaimer: CLDR maintains an LTS release with Phoenix 5.1 and HBase 2.2,
> > so it would make life a bit harder for us, too.
> >
> > Istvan
> >
> > On Wed, Oct 18, 2023 at 6:57 AM Viraj Jasani  wrote:
> >
> > > Thank you for the response, Rajeshbabu.
> > >
> > > > Bump up  Omid to 1.1.0
> > >
> > > Sounds good.
> > >
> > >
> > > > Remove the support of HBase versions <2.3.x
> > >
> > > Those versions are long EOL'ed so yes perhaps it makes sense to drop
> > their
> > > support, though I am not sure if we need to manage compatibility for
> the
> > > patch release.
> > > If we have consensus, it's fine to remove them. No strong opinion
> either
> > > way but I am slightly inclined to remove the support since they are
> > already
> > > EOL'ed.
> > >
> > > 2.3 is also EOL'ed, but we should keep it anyway since it was a stable
> > > release line for quite some time and some users might still be using
> > 2.3.x
> > > versions.
> > >
> > >
> > > On Tue, Oct 17, 2023 at 9:38 PM rajeshb...@apache.org <
> > > chrajeshbab...@gmail.com> wrote:
> > >
> > > > +1
> > > >
> > > > Would be better to do few things before release.
> > > > 1) Bump up  Omid to 1.1.0
> > > > 2) Remove the support of HBase versions <2.3.x
> > > >
> > > > These would just backports . I will do it if it's fine.
> > > >
> > > > Thanks,
> > > >
> > > >
> > > > On Wed, Oct 18, 2023 at 9:14 AM Viraj Jasani 
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > It's been almost a year since we had the last patch release on the
> > 5.1
> > > > > release line. As discussed on other threads, 5.2 release can wait a
> > > > little
> > > > > longer for some of the features that are in progress. In the
> > meantime,
> > > we
> > > > > should also keep the 5.1 release line active.
> > > > >
> > > > > We have some good contributions on the 5.1 release line. Unless
> > anyone
> > > > > would like to be the RM for 5.1.4, I would volunteer to start the
> > > release
> > > > > preparation early next week.
> > > > >
> > > >
> > >
> >
> >
> > --
> > *István Tóth* | Sr. Staff Software Engineer
> > *Email*: st...@cloudera.com
> > cloudera.com 
> > [image: Cloudera] 
> > [image: Cloudera on Twitter]  [image:
> > Cloudera on Facebook]  [image:
> Cloudera
> > on LinkedIn] 
> > --
> > --
> >
>

[jira] [Assigned] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook should delay executing truncate stats

[Viraj Jasani (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reassigned PHOENIX-7076:
-

Assignee: Divneet Kaur

> MetaDataRegionObserver#postOpen hook should delay executing truncate stats
> --
>
> Key: PHOENIX-7076
> URL: https://issues.apache.org/jira/browse/PHOENIX-7076
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.3
>Reporter: Viraj Jasani
>Assignee: Divneet Kaur
>Priority: Major
> Fix For: 5.2.0, 5.1.4
>
>
> For older versions upgrading to 4.7+, we perform deletion of all rows on 
> SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" 
> does not exist on SYSTEM.CATALOG.
> Since this task is performed in a daemon thread as part of region#postOpen 
> coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
> open gets delayed for some reason.
> Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial 
> delay (by default), we should perform truncate stats as a delayed task, even 
> though it does not require any repetition.
>  
> {code:java}
> 2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
> n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163)
>  
>     at 
> org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
>  
>     at 
> org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
>  
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
>     at 
> org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
>  
>     at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
>  
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
>     at 
> org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
>  
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.security.AccessController.doPrivileged(Native Method) 
>     at javax.security.auth.Subject.doAs(Subject.java:422) 
>     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
>  
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>     at java.lang.reflect.Method.invoke(Method.java:498) 
>     at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
>     at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.lang.Thread.run(Thread.java:750) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook should delay executing truncate stats

[Viraj Jasani (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reassigned PHOENIX-7076:
-

Assignee: (was: Viraj Jasani)

> MetaDataRegionObserver#postOpen hook should delay executing truncate stats
> --
>
> Key: PHOENIX-7076
> URL: https://issues.apache.org/jira/browse/PHOENIX-7076
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.3
>Reporter: Viraj Jasani
>Priority: Major
> Fix For: 5.2.0, 5.1.4
>
>
> For older versions upgrading to 4.7+, we perform deletion of all rows on 
> SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" 
> does not exist on SYSTEM.CATALOG.
> Since this task is performed in a daemon thread as part of region#postOpen 
> coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
> open gets delayed for some reason.
> Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial 
> delay (by default), we should perform truncate stats as a delayed task, even 
> though it does not require any repetition.
>  
> {code:java}
> 2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
> n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163)
>  
>     at 
> org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
>  
>     at 
> org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
>  
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
>     at 
> org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
>  
>     at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
>  
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
>     at 
> org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
>  
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.security.AccessController.doPrivileged(Native Method) 
>     at javax.security.auth.Subject.doAs(Subject.java:422) 
>     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
>  
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>     at java.lang.reflect.Method.invoke(Method.java:498) 
>     at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
>     at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.lang.Thread.run(Thread.java:750) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook should delay executing truncate stats

[Viraj Jasani (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reassigned PHOENIX-7076:
-

Assignee: Viraj Jasani

> MetaDataRegionObserver#postOpen hook should delay executing truncate stats
> --
>
> Key: PHOENIX-7076
> URL: https://issues.apache.org/jira/browse/PHOENIX-7076
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.3
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 5.2.0, 5.1.4
>
>
> For older versions upgrading to 4.7+, we perform deletion of all rows on 
> SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" 
> does not exist on SYSTEM.CATALOG.
> Since this task is performed in a daemon thread as part of region#postOpen 
> coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
> open gets delayed for some reason.
> Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial 
> delay (by default), we should perform truncate stats as a delayed task, even 
> though it does not require any repetition.
>  
> {code:java}
> 2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
> n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163)
>  
>     at 
> org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
>  
>     at 
> org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
>  
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
>     at 
> org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
>  
>     at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
>  
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
>     at 
> org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
>  
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.security.AccessController.doPrivileged(Native Method) 
>     at javax.security.auth.Subject.doAs(Subject.java:422) 
>     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
>  
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>     at java.lang.reflect.Method.invoke(Method.java:498) 
>     at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
>     at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.lang.Thread.run(Thread.java:750) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook should delay executing truncate stats

[Viraj Jasani (Jira)]

Viraj Jasani created PHOENIX-7076:
-

 Summary: MetaDataRegionObserver#postOpen hook should delay 
executing truncate stats
 Key: PHOENIX-7076
 URL: https://issues.apache.org/jira/browse/PHOENIX-7076
 Project: Phoenix
  Issue Type: Bug
Reporter: Viraj Jasani


For older versions upgrading to 4.7+, we perform deletion of all rows on 
SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" does 
not exist on SYSTEM.CATALOG.

Since this task is performed in a daemon thread as part of region#postOpen 
coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
open gets delayed for some reason.

Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial delay 
(by default), we should perform truncate stats as a delayed task, even though 
it does not require any repetition.

 
{code:java}
2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163) 
    at 
org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
 
    at 
org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
 
    at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
    at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
    at 
org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
 
    at 
org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
 
    at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
    at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
    at org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
    at 
org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
 
    at 
org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
 
    at java.security.AccessController.doPrivileged(Native Method) 
    at javax.security.auth.Subject.doAs(Subject.java:422) 
    at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
 
    at org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
    at 
org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
    at java.lang.reflect.Method.invoke(Method.java:498) 
    at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
    at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
    at 
org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
 
    at java.lang.Thread.run(Thread.java:750) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook should delay executing truncate stats

[Viraj Jasani (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-7076:
--
Fix Version/s: 5.2.0
   5.1.4

> MetaDataRegionObserver#postOpen hook should delay executing truncate stats
> --
>
> Key: PHOENIX-7076
> URL: https://issues.apache.org/jira/browse/PHOENIX-7076
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.3
>Reporter: Viraj Jasani
>Priority: Major
> Fix For: 5.2.0, 5.1.4
>
>
> For older versions upgrading to 4.7+, we perform deletion of all rows on 
> SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" 
> does not exist on SYSTEM.CATALOG.
> Since this task is performed in a daemon thread as part of region#postOpen 
> coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
> open gets delayed for some reason.
> Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial 
> delay (by default), we should perform truncate stats as a delayed task, even 
> though it does not require any repetition.
>  
> {code:java}
> 2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
> n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163)
>  
>     at 
> org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
>  
>     at 
> org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
>  
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
>     at 
> org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
>  
>     at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
>  
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
>     at 
> org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
>  
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.security.AccessController.doPrivileged(Native Method) 
>     at javax.security.auth.Subject.doAs(Subject.java:422) 
>     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
>  
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>     at java.lang.reflect.Method.invoke(Method.java:498) 
>     at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
>     at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.lang.Thread.run(Thread.java:750) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook should delay executing truncate stats

[Viraj Jasani (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-7076:
--
Affects Version/s: 5.1.3

> MetaDataRegionObserver#postOpen hook should delay executing truncate stats
> --
>
> Key: PHOENIX-7076
> URL: https://issues.apache.org/jira/browse/PHOENIX-7076
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.3
>Reporter: Viraj Jasani
>Priority: Major
>
> For older versions upgrading to 4.7+, we perform deletion of all rows on 
> SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" 
> does not exist on SYSTEM.CATALOG.
> Since this task is performed in a daemon thread as part of region#postOpen 
> coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
> open gets delayed for some reason.
> Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial 
> delay (by default), we should perform truncate stats as a delayed task, even 
> though it does not require any repetition.
>  
> {code:java}
> 2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
> n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163)
>  
>     at 
> org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
>  
>     at 
> org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
>  
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
>     at 
> org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
>  
>     at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
>  
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
>     at 
> org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
>  
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.security.AccessController.doPrivileged(Native Method) 
>     at javax.security.auth.Subject.doAs(Subject.java:422) 
>     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
>  
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>     at java.lang.reflect.Method.invoke(Method.java:498) 
>     at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
>     at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.lang.Thread.run(Thread.java:750) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7075) Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated PHOENIX-7075:

Fix Version/s: (was: 5.2.0)

> Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1
> --
>
> Key: PHOENIX-7075
> URL: https://issues.apache.org/jira/browse/PHOENIX-7075
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> As discussed in mail thread, this is to backport PHOENIX-6715 to branch 5.1.
> FYI [~rajeshbabu]
> CC: [~vjasani] [~stoty]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7075) Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated PHOENIX-7075:

Description: 
As discussed in mail thread, this is to backport PHOENIX-6715 to branch 5.1.

FYI [~rajeshbabu]

CC: [~vjasani] [~stoty]

  was:As discussed in mail thread, this is to backport 


> Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1
> --
>
> Key: PHOENIX-7075
> URL: https://issues.apache.org/jira/browse/PHOENIX-7075
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 5.2.0
>
>
> As discussed in mail thread, this is to backport PHOENIX-6715 to branch 5.1.
> FYI [~rajeshbabu]
> CC: [~vjasani] [~stoty]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7075) Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch 5.1

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated PHOENIX-7075:

Summary: Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch 5.1  (was: 
Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1)

> Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch 5.1
> --
>
> Key: PHOENIX-7075
> URL: https://issues.apache.org/jira/browse/PHOENIX-7075
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> As discussed in mail thread, this is to backport PHOENIX-6715 to branch 5.1.
> FYI [~rajeshbabu]
> CC: [~vjasani] [~stoty]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7075) Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated PHOENIX-7075:

Description: As discussed in mail thread, this is to backport   (was: We 
should release Omid 1.1.0 , and update Phoenix to it for 5.2)

> Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1
> --
>
> Key: PHOENIX-7075
> URL: https://issues.apache.org/jira/browse/PHOENIX-7075
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 5.2.0
>
>
> As discussed in mail thread, this is to backport 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (PHOENIX-7075) Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain reassigned PHOENIX-7075:
---

Assignee: Nihal Jain  (was: Istvan Toth)

> Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1
> --
>
> Key: PHOENIX-7075
> URL: https://issues.apache.org/jira/browse/PHOENIX-7075
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 5.2.0
>
>
> We should release Omid 1.1.0 , and update Phoenix to it for 5.2



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7075) Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1

[Nihal Jain (Jira)]

Nihal Jain created PHOENIX-7075:
---

 Summary: Backport PHOENIX-6715 “Update Omid to 1.1.0” to branch-5.1
 Key: PHOENIX-7075
 URL: https://issues.apache.org/jira/browse/PHOENIX-7075
 Project: Phoenix
  Issue Type: Task
  Components: core
Reporter: Nihal Jain
Assignee: Istvan Toth
 Fix For: 5.2.0


We should release Omid 1.1.0 , and update Phoenix to it for 5.2



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (OMID-251) Bump license-maven-plugin to latest version

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated OMID-251:

Description: 
In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to 
{{{}2.11{}}}, which was last updated 5 years ago. The plugin 
{{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.

See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
{code:java}
Downloading from central: 
[https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
{code}
In my org, when trying to build phoenix-omid, build fails as 
{{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.

The goal of this JIRA is to bump the afore-mentioned plugin to latest version, 
i.e. [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
which does not pull the log4j:log4j jar.

Full run log, for reference, of {{mvn license:check}} command after clearning 
\{{~/.m2/reposiitory} with version:
 * {{{}2.11{}}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
 * {{{}4.3{}}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.

  was:
In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
which was last updated 5 years ago. The plugin 
{{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.

See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
{code:java}
Downloading from central: 
[https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
{code}
In my org, when trying to build phoenix-omid, build fails as 
{{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.

The goal of this JIRA is to bump the afore-mentioned mentioned plugin to latest 
version, i.e. 
[4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], which 
does not pull the log4j:log4j jar.

Full run log of {{mvn license:check}} command after clearning 
\{{~/.m2/reposiitory} with
 * {{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
 * {{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.


> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to 
> {{{}2.11{}}}, which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned plugin to latest 
> version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log, for reference, of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with version:
>  * {{{}2.11{}}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{{}4.3{}}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-251) Bump license-maven-plugin to latest version

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776870#comment-17776870
 ] 

ASF GitHub Bot commented on OMID-251:
-

NihalJain commented on PR #142:
URL: https://github.com/apache/phoenix-omid/pull/142#issuecomment-1769194056

   Tested by first introducing as license error by deleting header from one of 
existing java file and then running `mvn license:check` both with/without 
change. Build failed in both cases as expected.




> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
> which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned mentioned plugin to 
> latest version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with
>  * {{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-251) Bump license-maven-plugin to latest version

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776867#comment-17776867
 ] 

ASF GitHub Bot commented on OMID-251:
-

NihalJain opened a new pull request, #142:
URL: https://github.com/apache/phoenix-omid/pull/142

   (no comment)




> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
> which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned mentioned plugin to 
> latest version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with
>  * {{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-251) Bump license-maven-plugin to latest version

[Nihal Jain (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776864#comment-17776864
 ] 

Nihal Jain commented on OMID-251:
-

Will submit a patch for same. [~stoty]  could you please add me as a 
contributor?

> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
> which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with v{{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory. 
> The goal of this JIRA is to bump the afore-mentioned mentioned plugin to 
> latest version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with
>  * v{{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * v{{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (OMID-251) Bump license-maven-plugin to latest version

[Nihal Jain (Jira)]

 [ 
https://issues.apache.org/jira/browse/OMID-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated OMID-251:

Description: 
In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
which was last updated 5 years ago. The plugin 
{{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.

See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
{code:java}
Downloading from central: 
[https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
{code}
In my org, when trying to build phoenix-omid, build fails as 
{{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.

The goal of this JIRA is to bump the afore-mentioned mentioned plugin to latest 
version, i.e. 
[4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], which 
does not pull the log4j:log4j jar.

Full run log of {{mvn license:check}} command after clearning 
\{{~/.m2/reposiitory} with
 * {{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
 * {{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.

  was:
In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
which was last updated 5 years ago. The plugin 
{{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.

See sample from run of {{mvn license:check}} with v{{2.11}} is as follows:
{code:java}
Downloading from central: 
[https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
{code}

In my org, when trying to build phoenix-omid, build fails as 
{{log4j:logj:1.2.x}} is strictly banned in interanl artifactory. 

The goal of this JIRA is to bump the afore-mentioned mentioned plugin to latest 
version, i.e. 
[4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], which 
does not pull the log4j:log4j jar.

Full run log of {{mvn license:check}} command after clearning 
\{{~/.m2/reposiitory} with
 * v{{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
 * v{{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.


> Bump license-maven-plugin to latest version
> ---
>
> Key: OMID-251
> URL: https://issues.apache.org/jira/browse/OMID-251
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Nihal Jain
>Priority: Major
> Attachments: out_v2.11.txt, out_v4.3.txt
>
>
> In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
> which was last updated 5 years ago. The plugin 
> {{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.
> See sample from run of {{mvn license:check}} with {{2.11}} is as follows:
> {code:java}
> Downloading from central: 
> [https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
> {code}
> In my org, when trying to build phoenix-omid, build fails as 
> {{log4j:logj:1.2.x}} is strictly banned in interanl artifactory.
> The goal of this JIRA is to bump the afore-mentioned mentioned plugin to 
> latest version, i.e. 
> [4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], 
> which does not pull the log4j:log4j jar.
> Full run log of {{mvn license:check}} command after clearning 
> \{{~/.m2/reposiitory} with
>  * {{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
>  * {{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (OMID-251) Bump license-maven-plugin to latest version

[Nihal Jain (Jira)]

Nihal Jain created OMID-251:
---

 Summary: Bump license-maven-plugin to latest version
 Key: OMID-251
 URL: https://issues.apache.org/jira/browse/OMID-251
 Project: Phoenix Omid
  Issue Type: Task
Reporter: Nihal Jain
 Attachments: out_v2.11.txt, out_v4.3.txt

In phoenix-omid pom.xml, {{maven-license-plugin.version}} is set to {{2.11}}, 
which was last updated 5 years ago. The plugin 
{{com.mycila:license-maven-plugin}} pulls log4j-1.2.x jar.

See sample from run of {{mvn license:check}} with v{{2.11}} is as follows:
{code:java}
Downloading from central: 
[https://repo.maven.apache.org/maven2/log4j/log4j/1.2.12/log4j-1.2.12.jar]
{code}

In my org, when trying to build phoenix-omid, build fails as 
{{log4j:logj:1.2.x}} is strictly banned in interanl artifactory. 

The goal of this JIRA is to bump the afore-mentioned mentioned plugin to latest 
version, i.e. 
[4.3|https://mvnrepository.com/artifact/com.mycila/license-maven-plugin], which 
does not pull the log4j:log4j jar.

Full run log of {{mvn license:check}} command after clearning 
\{{~/.m2/reposiitory} with
 * v{{2.11}}: [^out_v2.11.txt], which pulls {{log4j-1.2.x}} jar.
 * v{{4.3}}: [^out_v4.3.txt], which does not pull {{log4j-1.2.x}} jar.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Phoenix 5.1.4 release

[Viraj Jasani]

Sounds good Istvan, let’s keep the versions.

And thank you so much for fixing broken compilation for 2.1 and 2.2
versions:
https://github.com/apache/phoenix/pull/1714


On Tue, Oct 17, 2023 at 11:05 PM Istvan Toth 
wrote:

> I very much agree on the release.
>
> I don't remember why we didn't bump the Omid version in 5.1 after it was
> released.
> If it doesn't break anything, then it's a good thing.
>
> I disagree on removing the old HBase version support.
>
> Just as HBase doesn't remove support for old Hadoop versions in new patch
> (or even minor) releases,
> I think it would be much kinder to our users not to force them to upgrade
> HBase, when it really doesn't cost us
> much to maintain support for the old versions. (Even if the build with 2.1
> and 2.2 is broken now)
>
> I think that we should make an effort to increase Phoenix adoption beyond
> SFDC and the CLDR customer base.
> Making life easier for users of the Apache releases by not forcing an HBase
> upgrade is a step in that direction.
> Regular releases are also something that projects the image of a healthy
> project.
>
> Disclaimer: CLDR maintains an LTS release with Phoenix 5.1 and HBase 2.2,
> so it would make life a bit harder for us, too.
>
> Istvan
>
> On Wed, Oct 18, 2023 at 6:57 AM Viraj Jasani  wrote:
>
> > Thank you for the response, Rajeshbabu.
> >
> > > Bump up  Omid to 1.1.0
> >
> > Sounds good.
> >
> >
> > > Remove the support of HBase versions <2.3.x
> >
> > Those versions are long EOL'ed so yes perhaps it makes sense to drop
> their
> > support, though I am not sure if we need to manage compatibility for the
> > patch release.
> > If we have consensus, it's fine to remove them. No strong opinion either
> > way but I am slightly inclined to remove the support since they are
> already
> > EOL'ed.
> >
> > 2.3 is also EOL'ed, but we should keep it anyway since it was a stable
> > release line for quite some time and some users might still be using
> 2.3.x
> > versions.
> >
> >
> > On Tue, Oct 17, 2023 at 9:38 PM rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> > > +1
> > >
> > > Would be better to do few things before release.
> > > 1) Bump up  Omid to 1.1.0
> > > 2) Remove the support of HBase versions <2.3.x
> > >
> > > These would just backports . I will do it if it's fine.
> > >
> > > Thanks,
> > >
> > >
> > > On Wed, Oct 18, 2023 at 9:14 AM Viraj Jasani 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > It's been almost a year since we had the last patch release on the
> 5.1
> > > > release line. As discussed on other threads, 5.2 release can wait a
> > > little
> > > > longer for some of the features that are in progress. In the
> meantime,
> > we
> > > > should also keep the 5.1 release line active.
> > > >
> > > > We have some good contributions on the 5.1 release line. Unless
> anyone
> > > > would like to be the RM for 5.1.4, I would volunteer to start the
> > release
> > > > preparation early next week.
> > > >
> > >
> >
>
>
> --
> *István Tóth* | Sr. Staff Software Engineer
> *Email*: st...@cloudera.com
> cloudera.com 
> [image: Cloudera] 
> [image: Cloudera on Twitter]  [image:
> Cloudera on Facebook]  [image: Cloudera
> on LinkedIn] 
> --
> --
>

[jira] [Updated] (PHOENIX-7060) Compilation fails on 5.1 with Hbase 2.1 or 2.2

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-7060:
-
Affects Version/s: 5.2.0

> Compilation fails on 5.1 with Hbase 2.1 or 2.2
> --
>
> Key: PHOENIX-7060
> URL: https://issues.apache.org/jira/browse/PHOENIX-7060
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.2.0, 5.1.4
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
>
> Looks like PHOENIX-7039 needs some compatibility module encapsulation for the 
> new logic.
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
> (default-compile) on project phoenix-core: Compilation failure: Compilation 
> failure: 
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[40,40]
>  cannot find symbol
> [ERROR]   symbol:   class BlockCacheFactory
> [ERROR]   location: package org.apache.hadoop.hbase.io.hfile
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[132,21]
>  
> newHRegion(org.apache.hadoop.fs.Path,org.apache.hadoop.hbase.wal.WAL,org.apache.hadoop.fs.FileSystem,org.apache.hadoop.conf.Configuration,org.apache.hadoop.hbase.client.RegionInfo,org.apache.hadoop.hbase.client.TableDescriptor,org.apache.hadoop.hbase.regionserver.RegionServerServices)
>  is not public in org.apache.hadoop.hbase.regionserver.HRegion; cannot be 
> accessed from outside package
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[134,11]
>  cannot find symbol
> [ERROR]   symbol:   method setRestoredRegion(boolean)
> [ERROR]   location: variable region of type 
> org.apache.hadoop.hbase.regionserver.HRegion
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[138,14]
>  cannot find symbol
> [ERROR]   symbol:   variable BlockCacheFactory
> [ERROR]   location: class org.apache.phoenix.iterate.SnapshotScanner
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[139,31]
>  cannot find symbol
> [ERROR]   symbol:   variable HFILE_ONHEAP_BLOCK_CACHE_FIXED_SIZE_KEY
> [ERROR]   location: class org.apache.hadoop.hbase.HConstants
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[140,38]
>  cannot find symbol
> [ERROR]   symbol:   variable 
> HBASE_CLIENT_SCANNER_ONHEAP_BLOCK_CACHE_FIXED_SIZE_DEFAULT
> [ERROR]   location: class org.apache.hadoop.hbase.HConstants
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[143,26]
>  cannot find symbol
> [ERROR]   symbol:   variable BlockCacheFactory
> [ERROR]   location: class org.apache.phoenix.iterate.SnapshotScanner
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[148,11]
>  cannot find symbol
> [ERROR]   symbol:   method 
> setMobFileCache(org.apache.hadoop.hbase.mob.MobFileCache)
> [ERROR]   location: variable region of type 
> org.apache.hadoop.hbase.regionserver.HRegion{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (PHOENIX-7060) Compilation fails on 5.1 with Hbase 2.1 or 2.2

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth reassigned PHOENIX-7060:


Assignee: Istvan Toth  (was: Viraj Jasani)

> Compilation fails on 5.1 with Hbase 2.1 or 2.2
> --
>
> Key: PHOENIX-7060
> URL: https://issues.apache.org/jira/browse/PHOENIX-7060
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.4
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
>
> Looks like PHOENIX-7039 needs some compatibility module encapsulation for the 
> new logic.
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
> (default-compile) on project phoenix-core: Compilation failure: Compilation 
> failure: 
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[40,40]
>  cannot find symbol
> [ERROR]   symbol:   class BlockCacheFactory
> [ERROR]   location: package org.apache.hadoop.hbase.io.hfile
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[132,21]
>  
> newHRegion(org.apache.hadoop.fs.Path,org.apache.hadoop.hbase.wal.WAL,org.apache.hadoop.fs.FileSystem,org.apache.hadoop.conf.Configuration,org.apache.hadoop.hbase.client.RegionInfo,org.apache.hadoop.hbase.client.TableDescriptor,org.apache.hadoop.hbase.regionserver.RegionServerServices)
>  is not public in org.apache.hadoop.hbase.regionserver.HRegion; cannot be 
> accessed from outside package
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[134,11]
>  cannot find symbol
> [ERROR]   symbol:   method setRestoredRegion(boolean)
> [ERROR]   location: variable region of type 
> org.apache.hadoop.hbase.regionserver.HRegion
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[138,14]
>  cannot find symbol
> [ERROR]   symbol:   variable BlockCacheFactory
> [ERROR]   location: class org.apache.phoenix.iterate.SnapshotScanner
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[139,31]
>  cannot find symbol
> [ERROR]   symbol:   variable HFILE_ONHEAP_BLOCK_CACHE_FIXED_SIZE_KEY
> [ERROR]   location: class org.apache.hadoop.hbase.HConstants
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[140,38]
>  cannot find symbol
> [ERROR]   symbol:   variable 
> HBASE_CLIENT_SCANNER_ONHEAP_BLOCK_CACHE_FIXED_SIZE_DEFAULT
> [ERROR]   location: class org.apache.hadoop.hbase.HConstants
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[143,26]
>  cannot find symbol
> [ERROR]   symbol:   variable BlockCacheFactory
> [ERROR]   location: class org.apache.phoenix.iterate.SnapshotScanner
> [ERROR] 
> /home/stoty/workspaces/apache-phoenix/phoenix/phoenix-core/src/main/java/org/apache/phoenix/iterate/SnapshotScanner.java:[148,11]
>  cannot find symbol
> [ERROR]   symbol:   method 
> setMobFileCache(org.apache.hadoop.hbase.mob.MobFileCache)
> [ERROR]   location: variable region of type 
> org.apache.hadoop.hbase.regionserver.HRegion{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-6967) Aggregate query execution is not properly parallelized

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-6967:
-
Summary: Aggregate query execution is not properly parallelized  (was: 
Aggregate queries are not properly parallelized)

> Aggregate query execution is not properly parallelized
> --
>
> Key: PHOENIX-6967
> URL: https://issues.apache.org/jira/browse/PHOENIX-6967
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.2.0, 5.1.3
>Reporter: Istvan Toth
>Priority: Major
>
> The empty CQ generation after create table is not run in parallel.
> At first, I can see the reads and writes on happening on each region, but 
> after a minute or so, only one region is processed at a time in ascending 
> order.
> My guess is that it has something to do with keepalive/chunked results not 
> being processed on the client side correctly.
> I also suspect that this is not really specific to PostDDLMutationPlan, and 
> all queries where a single chunk takes a lot of time would be affected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-6967) Aggregate queries are not properly parallelized

[Istvan Toth (Jira)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-6967:
-
Summary: Aggregate queries are not properly parallelized  (was: Empty cell 
generation in PostdDDLMutationPlan is executed serially)

> Aggregate queries are not properly parallelized
> ---
>
> Key: PHOENIX-6967
> URL: https://issues.apache.org/jira/browse/PHOENIX-6967
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.2.0, 5.1.3
>Reporter: Istvan Toth
>Priority: Major
>
> The empty CQ generation after create table is not run in parallel.
> At first, I can see the reads and writes on happening on each region, but 
> after a minute or so, only one region is processed at a time in ascending 
> order.
> My guess is that it has something to do with keepalive/chunked results not 
> being processed on the client side correctly.
> I also suspect that this is not really specific to PostDDLMutationPlan, and 
> all queries where a single chunk takes a lot of time would be affected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Phoenix 5.1.4 release

[Istvan Toth]

I very much agree on the release.

I don't remember why we didn't bump the Omid version in 5.1 after it was
released.
If it doesn't break anything, then it's a good thing.

I disagree on removing the old HBase version support.

Just as HBase doesn't remove support for old Hadoop versions in new patch
(or even minor) releases,
I think it would be much kinder to our users not to force them to upgrade
HBase, when it really doesn't cost us
much to maintain support for the old versions. (Even if the build with 2.1
and 2.2 is broken now)

I think that we should make an effort to increase Phoenix adoption beyond
SFDC and the CLDR customer base.
Making life easier for users of the Apache releases by not forcing an HBase
upgrade is a step in that direction.
Regular releases are also something that projects the image of a healthy
project.

Disclaimer: CLDR maintains an LTS release with Phoenix 5.1 and HBase 2.2,
so it would make life a bit harder for us, too.

Istvan

On Wed, Oct 18, 2023 at 6:57 AM Viraj Jasani  wrote:

> Thank you for the response, Rajeshbabu.
>
> > Bump up  Omid to 1.1.0
>
> Sounds good.
>
>
> > Remove the support of HBase versions <2.3.x
>
> Those versions are long EOL'ed so yes perhaps it makes sense to drop their
> support, though I am not sure if we need to manage compatibility for the
> patch release.
> If we have consensus, it's fine to remove them. No strong opinion either
> way but I am slightly inclined to remove the support since they are already
> EOL'ed.
>
> 2.3 is also EOL'ed, but we should keep it anyway since it was a stable
> release line for quite some time and some users might still be using 2.3.x
> versions.
>
>
> On Tue, Oct 17, 2023 at 9:38 PM rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > +1
> >
> > Would be better to do few things before release.
> > 1) Bump up  Omid to 1.1.0
> > 2) Remove the support of HBase versions <2.3.x
> >
> > These would just backports . I will do it if it's fine.
> >
> > Thanks,
> >
> >
> > On Wed, Oct 18, 2023 at 9:14 AM Viraj Jasani  wrote:
> >
> > > Hi,
> > >
> > > It's been almost a year since we had the last patch release on the 5.1
> > > release line. As discussed on other threads, 5.2 release can wait a
> > little
> > > longer for some of the features that are in progress. In the meantime,
> we
> > > should also keep the 5.1 release line active.
> > >
> > > We have some good contributions on the 5.1 release line. Unless anyone
> > > would like to be the RM for 5.1.4, I would volunteer to start the
> release
> > > preparation early next week.
> > >
> >
>


-- 
*István Tóth* | Sr. Staff Software Engineer
*Email*: st...@cloudera.com
cloudera.com 
[image: Cloudera] 
[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 
--
--