[jira] [Updated] (PHOENIX-5811) Synchronise Phoenix dependencies to match Hbase dependency versions
[ https://issues.apache.org/jira/browse/PHOENIX-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5811: --- Attachment: PHOENIX-5811.master.v4.patch > Synchronise Phoenix dependencies to match Hbase dependency versions > --- > > Key: PHOENIX-5811 > URL: https://issues.apache.org/jira/browse/PHOENIX-5811 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5811.master.v1.patch, > PHOENIX-5811.master.v2.patch, PHOENIX-5811.master.v3.patch, > PHOENIX-5811.master.v4.patch > > > Phoenix uses an older version of some dependencies. > We could reduce the number of dependencies by using the same versions as > Hbase. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5789) try to standardize on a JSON library
[ https://issues.apache.org/jira/browse/PHOENIX-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5789: --- Attachment: PHOENIX-5789.master.v2.patch > try to standardize on a JSON library > > > Key: PHOENIX-5789 > URL: https://issues.apache.org/jira/browse/PHOENIX-5789 > Project: Phoenix > Issue Type: Improvement > Components: core >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Minor > Attachments: PHOENIX-5789.master.v1.patch, > PHOENIX-5789.master.v2.patch > > > Phoenix uses at least the following JSON libraries: > * gson > * jackson > * jettison > Of these, only the jackson usage is performance critical, as it is used > during bulk loading. > Try to standardize on a single one to reduce dependency hell. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSS] Maven repo inside PQS for client jars
Hi, Over in HBASE-24066, I had hacked together a POC which shows the HBase UI hosting shaded client jars for Maven-based users. Nick had raised some concerns about inadvertently impacting the HBase Master, so it's stalled out at this point. https://issues.apache.org/jira/browse/HBASE-24066 I'm curious what folks in Phoenix think about doing this inside of PQS. The idea would be that you can specify a path beneath the PQS url in your Maven application and automatically pull jars from there. The benefit would be that clients can automatically write their code and pull the exact client JAR for the cluster they're talking to. If there aren't concerns, I'll implement the same idea over here. I want to avoid doing the work if it will just sit in limbo. - Josh
[jira] [Created] (PHOENIX-5823) Clean up phoenix-client vestiges from a non-attached jar
Josh Elser created PHOENIX-5823: --- Summary: Clean up phoenix-client vestiges from a non-attached jar Key: PHOENIX-5823 URL: https://issues.apache.org/jira/browse/PHOENIX-5823 Project: Phoenix Issue Type: Task Reporter: Josh Elser Assignee: Josh Elser Noticed that phoenix-client is doing some goofy stuff still as a result of the old way where we didn't attach the phoenix-client.jar to the Maven project (e.g. created the jar in target but didn't publish the jar out of our build). Can remove some unnecessary stuff in the pom.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5754) Phoenix IT tests are failing in Precommit QA build randomly.
[ https://issues.apache.org/jira/browse/PHOENIX-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5754. -- Resolution: Fixed I haven't seen a test job killed outright since the fix went in. The tests are still horribly flakey, but that's a different issue. > Phoenix IT tests are failing in Precommit QA build randomly. > > > Key: PHOENIX-5754 > URL: https://issues.apache.org/jira/browse/PHOENIX-5754 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.16.0 >Reporter: Neha Gupta >Assignee: Istvan Toth >Priority: Blocker > Labels: build-failure, precommit > > While running Phoenix IT tests in QA, JVM is getting killed for random tests. > QA stops the run and mark that build failed. Related [jenkins builds| > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3520/console]] does > not give any information about the failure. We are blocked on committing > patches until this issue is fixed. > This behavior was observed in [PHOENIX-5496|#comment-17048460] and > [PHOENIX-5698|#comment-17049989] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5822) Move Python driver to queryserver repo
Istvan Toth created PHOENIX-5822: Summary: Move Python driver to queryserver repo Key: PHOENIX-5822 URL: https://issues.apache.org/jira/browse/PHOENIX-5822 Project: Phoenix Issue Type: Task Components: core, queryserver Affects Versions: 5.1.0, queryserver-1.0.0, 4.x Reporter: Istvan Toth Assignee: Istvan Toth The python phoenix driver in the python repo is in fact a queryserver client. It should be relocated to the phoenix-queryserver repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5642) Add HTTPS support to Phoenix Query Server and thin client
[ https://issues.apache.org/jira/browse/PHOENIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5642: - Fix Version/s: (was: 5.1.0) queryserver-1.0.0 > Add HTTPS support to Phoenix Query Server and thin client > - > > Key: PHOENIX-5642 > URL: https://issues.apache.org/jira/browse/PHOENIX-5642 > Project: Phoenix > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5642.docs.v1.patch > > Time Spent: 20m > Remaining Estimate: 0h > > PQS does not support HTTPS at the moment. The thin client does, but it has > some limitations that it inherits from avatica. > This task is mostly about exposing the HTTPS functionality in avatica via PQS. > There are a number authentication features that avatica 1.12 does not support > over https, so in order to take full advantage of this feature, updating > avatica to 1.16 is also necessary. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5702) Add https support to sqlline-thin script
[ https://issues.apache.org/jira/browse/PHOENIX-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5702: - Fix Version/s: queryserver-1.0.0 > Add https support to sqlline-thin script > > > Key: PHOENIX-5702 > URL: https://issues.apache.org/jira/browse/PHOENIX-5702 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We have added https support to Phoenix Query Server. > Using it requires specifying the keystore file and keystore password in the > URL. > While it is possible to specify these parameteres with the current > sqlline-thin script, it is not intuitive and error-prone. > Add explicit support for specifying the keystore and keystore password to > sqlline-thin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5680) remove psql.py from phoenix-queryserver
[ https://issues.apache.org/jira/browse/PHOENIX-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5680: - Fix Version/s: (was: 5.1.0) queryserver-1.0.0 > remove psql.py from phoenix-queryserver > --- > > Key: PHOENIX-5680 > URL: https://issues.apache.org/jira/browse/PHOENIX-5680 > Project: Phoenix > Issue Type: Task >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > Fix For: queryserver-1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The phoenix-queryserver repo duplicates the bin/psql.py file from the core > phoenix repo, for no apparent reason. > Remove it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5670) Add the neccesary Synchronisation to the tests in the PQS repo
[ https://issues.apache.org/jira/browse/PHOENIX-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5670: - Fix Version/s: (was: 5.1.0) queryserver-1.0.0 > Add the neccesary Synchronisation to the tests in the PQS repo > -- > > Key: PHOENIX-5670 > URL: https://issues.apache.org/jira/browse/PHOENIX-5670 > Project: Phoenix > Issue Type: Bug >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to do add the same synchronisation that we added in PHOENIX-5554 for > the core repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5761) sqlline-thin kerberos logic too aggressive
[ https://issues.apache.org/jira/browse/PHOENIX-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5761: - Fix Version/s: queryserver-1.0.0 > sqlline-thin kerberos logic too aggressive > -- > > Key: PHOENIX-5761 > URL: https://issues.apache.org/jira/browse/PHOENIX-5761 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The kerberos login in logic in SqllineWrapper.java tries to read the hbase > configuration, and tries to log in into kerberos if it decides that the HBase > instance is kerberized. > While this is fine in many use cases, it causes unintended failures in at > least the following cases: > * When trying to connect via Knox, which usually does not use kerberos > * When trying to connect to a a PQS that is not using the same HBase config > as the current host. > This is true even if the user explicitly specifies BASIC authentication. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5741) Spurious protobuf version property in queryserver-client pom
[ https://issues.apache.org/jira/browse/PHOENIX-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5741: - Fix Version/s: queryserver-1.0.0 Affects Version/s: (was: 1.0.0) queryserver-1.0.0 > Spurious protobuf version property in queryserver-client pom > > > Key: PHOENIX-5741 > URL: https://issues.apache.org/jira/browse/PHOENIX-5741 > Project: Phoenix > Issue Type: Bug >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Trivial > Fix For: queryserver-1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > During the Avatica upgrade, I did not upgrade the corresponding Avatica > version in the thin client pom. > While this does not seems to cause problems in normal operation, it does make > diagnosing some error conditions harder (NoSuchFile/Method exceptions instead > of more informative ones). > Use the protobuf version in Avatica (3.6.1 currently), either by manually > updating the version, or finding a way of selectively disabling version > management in the thin client module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5761) sqlline-thin kerberos logic too aggressive
[ https://issues.apache.org/jira/browse/PHOENIX-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5761: - Affects Version/s: (was: 4.16.0) (was: 5.1.0) queryserver-1.0.0 > sqlline-thin kerberos logic too aggressive > -- > > Key: PHOENIX-5761 > URL: https://issues.apache.org/jira/browse/PHOENIX-5761 > Project: Phoenix > Issue Type: Bug >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The kerberos login in logic in SqllineWrapper.java tries to read the hbase > configuration, and tries to log in into kerberos if it decides that the HBase > instance is kerberized. > While this is fine in many use cases, it causes unintended failures in at > least the following cases: > * When trying to connect via Knox, which usually does not use kerberos > * When trying to connect to a a PQS that is not using the same HBase config > as the current host. > This is true even if the user explicitly specifies BASIC authentication. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5794) Create a threshold for non async index creation, that can be modified in configs
[ https://issues.apache.org/jira/browse/PHOENIX-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5794: --- Attachment: PHOENIX-5794.4.x-HBase-1.5.v1.patch PHOENIX-5794.4.x-HBase-1.3.v1.patch > Create a threshold for non async index creation, that can be modified in > configs > > > Key: PHOENIX-5794 > URL: https://issues.apache.org/jira/browse/PHOENIX-5794 > Project: Phoenix > Issue Type: Improvement >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5794.4.x-HBase-1.3.v1.patch, > PHOENIX-5794.4.x-HBase-1.5.v1.patch, PHOENIX-5794.master.v1.patch, > PHOENIX-5794.master.v10.patch, PHOENIX-5794.master.v2.patch, > PHOENIX-5794.master.v3.patch, PHOENIX-5794.master.v4.patch, > PHOENIX-5794.master.v5.patch, PHOENIX-5794.master.v6.patch, > PHOENIX-5794.master.v7.patch, PHOENIX-5794.master.v8.patch, > PHOENIX-5794.master.v9.patch > > > Issue: > When user try to create an index on a huge phoenix table the region servers > crashed which led to multiple regions going in RIT state. > > Solution: > If the expected byte read size is higher than the limit we raise an exception > to notify the user that the index should be created asynchronously. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
[ https://issues.apache.org/jira/browse/PHOENIX-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5454: - Fix Version/s: queryserver-1.0.0 > Phoenix scripts start foreground java processes as child processes > -- > > Key: PHOENIX-5454 > URL: https://issues.apache.org/jira/browse/PHOENIX-5454 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > Fix For: 5.1.0, queryserver-1.0.0, 4.16.0 > > Attachments: PHOENIX-5454.master.v1.patch, > PHOENIX-5454.master.v2.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently the phoenix scripts in python start the java process via > subprocess.call() or subprocess.popen() even when the java process has to run > in the foreground, and there is no cleanup required. > I propose that in these cases, we start java via os.exec*(). This has the > following advantages: > * There is no python process idling waiting for the java process to end, > reducing process count and memory consumption > * Signal handling is simplified (signals sent to the starting script are > received by the java process started) > * Return code handling is simplified (no need to check for and return error > codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5459) Enable running the test suite with JDK11
[ https://issues.apache.org/jira/browse/PHOENIX-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5459: - Fix Version/s: queryserver-1.0.0 connectors-1.0.0 > Enable running the test suite with JDK11 > > > Key: PHOENIX-5459 > URL: https://issues.apache.org/jira/browse/PHOENIX-5459 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, connectors-1.0.0, queryserver-1.0.0 > > Attachments: PHOENIX-5459.master.v1.patch > > Time Spent: 1h > Remaining Estimate: 0h > > As HBase runs on JDK11, Phoenix should also support JDK11. > A first step is making sure that we can run the tests on JDK11, while still > building on JDK8. > Right now, the test suite cannot be run with JDK11, because it tries to run > the failsafe tests with a VM setting that prevent JDK11 from starting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5794) Create a threshold for non async index creation, that can be modified in configs
[ https://issues.apache.org/jira/browse/PHOENIX-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5794: --- Comment: was deleted (was: There are the new patch files. Please apply the HBase 1.5 to the HBase 1.4 as well.) > Create a threshold for non async index creation, that can be modified in > configs > > > Key: PHOENIX-5794 > URL: https://issues.apache.org/jira/browse/PHOENIX-5794 > Project: Phoenix > Issue Type: Improvement >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5794.4.x-HBase-1.3.v1.patch, > PHOENIX-5794.4.x-HBase-1.5.v1.patch, PHOENIX-5794.master.v1.patch, > PHOENIX-5794.master.v10.patch, PHOENIX-5794.master.v2.patch, > PHOENIX-5794.master.v3.patch, PHOENIX-5794.master.v4.patch, > PHOENIX-5794.master.v5.patch, PHOENIX-5794.master.v6.patch, > PHOENIX-5794.master.v7.patch, PHOENIX-5794.master.v8.patch, > PHOENIX-5794.master.v9.patch > > > Issue: > When user try to create an index on a huge phoenix table the region servers > crashed which led to multiple regions going in RIT state. > > Solution: > If the expected byte read size is higher than the limit we raise an exception > to notify the user that the index should be created asynchronously. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5794) Create a threshold for non async index creation, that can be modified in configs
[ https://issues.apache.org/jira/browse/PHOENIX-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5794: --- Attachment: PHOENIX-5794.4.x.v1.patch > Create a threshold for non async index creation, that can be modified in > configs > > > Key: PHOENIX-5794 > URL: https://issues.apache.org/jira/browse/PHOENIX-5794 > Project: Phoenix > Issue Type: Improvement >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5794.4.x-HBase-1.3.v1.patch, > PHOENIX-5794.4.x-HBase-1.5.v1.patch, PHOENIX-5794.4.x.v1.patch, > PHOENIX-5794.master.v1.patch, PHOENIX-5794.master.v10.patch, > PHOENIX-5794.master.v2.patch, PHOENIX-5794.master.v3.patch, > PHOENIX-5794.master.v4.patch, PHOENIX-5794.master.v5.patch, > PHOENIX-5794.master.v6.patch, PHOENIX-5794.master.v7.patch, > PHOENIX-5794.master.v8.patch, PHOENIX-5794.master.v9.patch > > > Issue: > When user try to create an index on a huge phoenix table the region servers > crashed which led to multiple regions going in RIT state. > > Solution: > If the expected byte read size is higher than the limit we raise an exception > to notify the user that the index should be created asynchronously. -- This message was sent by Atlassian Jira (v8.3.4#803005)
