Re: [VOTE] Release of Apache Phoenix 5.2.0 RC6

[Viraj Jasani]

Once Omid is upgraded to 1.1.2 on Phoenix master and 5.2 branches, I would
be happy to start new RC for Phoenix 5.2.0 release sometime next week.


On Thu, Feb 29, 2024 at 10:45 AM Viraj Jasani  wrote:

> Thanks Istvan, Rajeshbabu and Lars for identifying, fixing and now
> starting with new Omid release.
> I will re-create RCs once upgraded Omid version is checked-in.
>
> In the meantime, if there is any important fix anyone thinks is worth
> including in 5.2.0, please let me know.
>
> This vote is now closed and the RC is rejected for the release purpose.
>
>
>
> On Thu, Feb 29, 2024 at 8:13 AM rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
>> Istvan,
>>
>> Sure, yes will do 1.1.2 release tomorrow.
>>
>> Thanks,
>> Rajeshbabu.
>>
>> On Thu, Feb 29, 2024, 9:40 PM Istvan Toth  wrote:
>>
>> > The fix for OMID-277 has landed (among with two other fixes)
>> >
>> > Is there a chance you could manage the Omid 1.2.1 release Rajeshbabu ?
>> >
>> > On Thu, Feb 29, 2024 at 7:10 AM Istvan Toth  wrote:
>> >
>> > > -1 We need a new Omid release first that fixes OMID-277 first
>> (binding)
>> > >
>> > > On Thu, Feb 29, 2024 at 6:57 AM Istvan Toth 
>> wrote:
>> > >
>> > >> I have done no testing yet, but
>> > >> https://issues.apache.org/jira/browse/OMID-277 looks like a blocker.
>> > >>
>> > >> On Wed, Feb 28, 2024 at 10:55 PM Viraj Jasani 
>> > wrote:
>> > >>
>> > >>> Please vote on this Apache Phoenix release candidate,
>> Phoenix-5.2.0RC6
>> > >>>
>> > >>> The VOTE will remain open for at least 72 hours.
>> > >>>
>> > >>> [ ] +1 Release this package as Apache Phoenix 5.2.0
>> > >>> [ ] -1 Do not release this package because ...
>> > >>>
>> > >>> The tag to be voted on is 5.2.0RC6:
>> > >>>
>> > >>>   https://github.com/apache/phoenix/tree/5.2.0RC6
>> > >>>
>> > >>> The release files, including signatures, digests, as well as
>> CHANGES.md
>> > >>> and RELEASENOTES.md included in this RC can be found at:
>> > >>>
>> > >>> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-5.2.0RC6/
>> > >>>
>> > >>> Maven artifacts are available in a staging repository at:
>> > >>>
>> > >>>
>> >
>> https://repository.apache.org/content/repositories/orgapachephoenix-1254/
>> > >>>
>> > >>> Artifacts were signed with the 1012D134 key which can be found in:
>> > >>>
>> > >>>   https://dist.apache.org/repos/dist/release/phoenix/KEYS
>> > >>>
>> > >>> To learn more about Apache Phoenix, please see
>> > >>>
>> > >>>   https://phoenix.apache.org/
>> > >>>
>> > >>> Thanks,
>> > >>> Your Phoenix Release Manager
>> > >>>
>> > >>
>> > >>
>> > >> --
>> > >> *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-7290) Cannot load or instantiate class org.apache.phoenix.query.DefaultGuidePostsCacheFactory

[Jeff (Jira)]

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

Jeff updated PHOENIX-7290:
--
Attachment: spring-jdbc_error_stack.txt
SQLSquirrel_error_stack.txt

> Cannot load or instantiate class 
> org.apache.phoenix.query.DefaultGuidePostsCacheFactory
> ---
>
> Key: PHOENIX-7290
> URL: https://issues.apache.org/jira/browse/PHOENIX-7290
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Jeff
>Priority: Major
> Attachments: SQLSquirrel_error_stack.txt, spring-jdbc_error_stack.txt
>
>
> Recently we're trying to update to phoenix 5.1.3 and we're running into an 
> issue.
> {code:java}
> org.apache.phoenix.exception.PhoenixNonRetryableRuntimeException: Could not 
> load/instantiate class org.apache.phoenix.query.DefaultGuidePostsCacheFactory 
> {code}
> I believe there are other areas where this has been brought up such as in SO:
> [https://stackoverflow.com/questions/73194696/phoenixnonretryableruntimeexception-could-not-load-instantiate-class-org-apache]
> The issue seems to have been introduced in 5.1.0, anything in 4.8 or below 
> seems to work fine.  
> Steps to reproduce:
>  # Use Squirrel SQL 4.7.1
>  # Create the drivers and load phoenix 5.1.3 into the class path
>  # Define alias and test connection



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

Re: [DISCUSS] reducing Github noise in the JIRA comment section

[Istvan Toth]

Opened https://issues.apache.org/jira/browse/PHOENIX-7292 with a PR.

I have also added some other fields and a few labels based on HBase.


On Sat, Mar 23, 2024 at 6:03 AM Viraj Jasani  wrote:

> +1, we can pursue the same settings from HBase, specifically the recent one
> notifies when PR is opened, but discussions are not commented to the Jira.
>
>
> On Thu, Mar 21, 2024 at 10:49 PM Istvan Toth  wrote:
>
> > A few years back I have changed the Github integration settings to write
> > all events as comments to the ticket.
> > In hindsight, this was a bad idea, as the tickets are now so noisy that
> > they are barely suitable for discussions.
> > I propose copying the relevant project settings from HBase, which seems
> to
> > be much more usable.
> >
> > WDYT ?
> >
> > Istvan
> >
>


-- 
*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-7292) Update .asf.yaml based on HBase

[Istvan Toth (Jira)]

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

Istvan Toth updated PHOENIX-7292:
-
Summary: Update .asf.yaml based on HBase  (was: Update .asf.yaml based on 
HBase's)

> Update .asf.yaml based on HBase
> ---
>
> Key: PHOENIX-7292
> URL: https://issues.apache.org/jira/browse/PHOENIX-7292
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> As discussed on the mailing list, the current settings result in far too 
> noisy JIRA tickets.



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

[jira] [Created] (PHOENIX-7292) Update .asf.yaml based on HBase's

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7292:


 Summary: Update .asf.yaml based on HBase's
 Key: PHOENIX-7292
 URL: https://issues.apache.org/jira/browse/PHOENIX-7292
 Project: Phoenix
  Issue Type: Improvement
  Components: core
Reporter: Istvan Toth
Assignee: Istvan Toth


As discussed on the mailing list, the current settings result in far too noisy 
JIRA tickets.



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

[jira] [Reopened] (PHOENIX-7250) Fix HBase log level in tests

[Istvan Toth (Jira)]

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

Istvan Toth reopened PHOENIX-7250:
--

Reopening as this didn't make it into 5.2.0.
We should backport it to 5.2 after the release at least.

> Fix HBase log level in tests
> 
>
> Key: PHOENIX-7250
> URL: https://issues.apache.org/jira/browse/PHOENIX-7250
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.2.0, 5.3.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>  Labels: test
> Fix For: 5.3.0
>
>
> When switching to log4j2, I made a typo in the logging config, which results
> in HBase log level being set to WARN, instead of DEBUG that it was previously.
> This makes debugging some test failures hard to impossbile.
> Fix this.



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

[jira] [Assigned] (PHOENIX-7288) Add unshaded connector JARs to connectors assembly

[Istvan Toth (Jira)]

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

Istvan Toth reassigned PHOENIX-7288:


Assignee: Istvan Toth

> Add unshaded connector JARs to connectors assembly
> --
>
> Key: PHOENIX-7288
> URL: https://issues.apache.org/jira/browse/PHOENIX-7288
> Project: Phoenix
>  Issue Type: Improvement
>  Components: connectors, hive-connector, spark-connector
>Affects Versions: connectors-6.0.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
>
> The new phoenix-mapreduce jar makes the shaded connectors JARs obsolete (at 
> least for Phoenix 5.2+)
> Add the unshaded JARs to the assembly, and also add an option to to build the 
> assembly without the shaded JARs.



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

[jira] [Resolved] (PHOENIX-7241) SaltedTableMergeBucketsIT is very slow on HBase 3.0

[Istvan Toth (Jira)]

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

Istvan Toth resolved PHOENIX-7241.
--
  Assignee: Istvan Toth
Resolution: Invalid

> SaltedTableMergeBucketsIT is very slow on HBase 3.0
> ---
>
> Key: PHOENIX-7241
> URL: https://issues.apache.org/jira/browse/PHOENIX-7241
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.3.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Minor
>
> it runs for more than 20 minutes, while it finishes in less than 10 with 
> HBase 2 (same machine)



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

[jira] [Commented] (OMID-277) Omid 1.1.2 fails with Phoenix 5.2

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on OMID-277:
-

soenkeliebau commented on PR #156:
URL: https://github.com/apache/phoenix-omid/pull/156#issuecomment-2022350366

   > I have successfully tested this on a pseudistributed cluster with Phoenix 
HEAD.
   
   Totally unrelated, just an fyi. We have hdfs, zookeeper and hbase (with 
phoenix) operators that are open source at Stackable that could potentially 
help you with testing environments here. Happy to spend a bit of time with you 
and investigate if we can come up with something to make your life easier if 
you are interested.




> Omid 1.1.2 fails with Phoenix 5.2
> -
>
> Key: OMID-277
> URL: https://issues.apache.org/jira/browse/OMID-277
> Project: Phoenix Omid
>  Issue Type: Bug
>Affects Versions: 1.1.1, 1.1.2
>Reporter: Lars Hofhansl
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 1.1.2
>
>
> Try to create a transactional table with Phoenix 5.2 and Omid 1.1.2, and 
> you'll find this in the RS log:
> {code:java}
>  2024-02-28T20:26:13,055 ERROR [RS_OPEN_REGION-regionserver/think:16020-2] 
> coprocessor.CoprocessorHost: The coprocessor 
> org.apache.phoenix.coprocessor.OmidTransactionalProcessor threw 
> java.lang.NoClassDefFoundE
> rror: Could not initialize class 
> org.apache.omid.committable.hbase.HBaseCommitTableConfig
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.omid.committable.hbase.HBaseCommitTableConfig
> at 
> org.apache.omid.transaction.OmidSnapshotFilter.start(OmidSnapshotFilter.java:85)
>  ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at 
> org.apache.phoenix.coprocessor.OmidTransactionalProcessor.start(OmidTransactionalProcessor.java:44)
>  ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at 
> org.apache.hadoop.hbase.coprocessor.BaseEnvironment.startup(BaseEnvironment.java:69)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:285)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:249)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:200)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.loadTableCoprocessors(RegionCoprocessorHost.java:388)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.(RegionCoprocessorHost.java:278)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at org.apache.hadoop.hbase.regionserver.HRegion.(HRegion.java:859) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at org.apache.hadoop.hbase.regionserver.HRegion.(HRegion.java:734) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
>  ~[?:?]
> at java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502) 
> ~[?:?]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:486) ~[?:?]
> at org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:6971) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegionFromTableDir(HRegion.java:7184)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7161) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7120) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7076) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler.process(AssignRegionHandler.java:149)
>  ~[hbase-server-2.5.7.jar:2.5.7]
> at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104) 
> ~[hbase-server-2.5.7.jar:2.5.7]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
>  ~[?:?]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
>  ~[?:?]
> at java.lang.Thread.run(Thread.java:1583) ~[?:?]
> Caused by: java.lang.ExceptionInInitializerError: Exception 
> java.lang.NoClassDefFoundError: 
> org/apache/phoenix/shaded/com/google/common/base/Charsets [in thread 
> "RS_OPEN_REGION-regionserver/think:16020-2"]
> at 
> org.apache.omid.committable.hbase.HBaseCommitTableConfig.(HBaseCommitTableConfig.java:36)
>  ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at org.apache.omid.transaction.OmidCompactor.start(OmidCompactor.java:92) 
> ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at 
> 

Community Over Code NA 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

[ You are receiving this email as a subscriber to one or more ASF project
dev or user
  mailing lists and is not being sent to you directly. It is important that
we reach all of our
  users and contributors/committers so that they may get a chance to
benefit from this.
  We apologise in advance if this doesn't interest you but it is on topic
for the mailing
  lists of the Apache Software Foundation; and it is important please that
you do not
  mark this as spam in your email client. Thank You! ]

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code NA 2024 are now
open!

We will be supporting Community over Code NA, Denver Colorado in
October 7th to the 10th 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Monday 6th May, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Denver, Colorado , October 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)