[jira] [Created] (PHOENIX-5896) Implement incremental rebuild along the failed regions in IndexTool
Swaroopa Kadam created PHOENIX-5896: --- Summary: Implement incremental rebuild along the failed regions in IndexTool Key: PHOENIX-5896 URL: https://issues.apache.org/jira/browse/PHOENIX-5896 Project: Phoenix Issue Type: Improvement Reporter: Swaroopa Kadam Assignee: Swaroopa Kadam As we run the index tool on indexes to be rebuilt after the upgrade, it spends some time in rescanning successful regions from the last rebuild. We want to make the index tool a little smarter to not rebuild rows from the regions that were found in the PIT_result table from the last rebuild. PIT_result logs region info if it was successfully rebuilt in the last run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5894) Table versus Table Full Outer join on Salted tables not working
[ https://issues.apache.org/jira/browse/PHOENIX-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-5894: - Attachment: (was: PHOENIX-5894.patch) > Table versus Table Full Outer join on Salted tables not working > --- > > Key: PHOENIX-5894 > URL: https://issues.apache.org/jira/browse/PHOENIX-5894 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.0.0 >Reporter: Ben Cohen >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5894.patch, > Salt_Bucketed_Table_Full_Outer_Join_Issue.docx > > > Trying to do a Full Outer Join on two tables. The operation works when the > tables are not salted but fails with an exception related to casting when > performed on the salted versions of the tables. Here is the exceptions: > "java.lang.ClassCastException: org.apache.phoenix.schema.PColumnImpl cannot > be cast to org.apache.phoenix.schema.ProjectedColumn > at > org.apache.phoenix.compile.JoinCompiler.joinProjectedTables(JoinCompiler.java:1256) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:425) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:228) > at > org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:191) > at > org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:153) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:490) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:456) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:302) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:291) > at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:290) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:283) > at > org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1830) > at sqlline.Commands.execute(Commands.java:822) > at sqlline.Commands.sql(Commands.java:732) > at sqlline.SqlLine.dispatch(SqlLine.java:813) > at sqlline.SqlLine.begin(SqlLine.java:686) > at sqlline.SqlLine.start(SqlLine.java:398) > at sqlline.SqlLine.main(SqlLine.java:291)" > I have attached a word document with the complete list of queries and their > results, along with commands to recreate the data. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5894) Table versus Table Full Outer join on Salted tables not working
[ https://issues.apache.org/jira/browse/PHOENIX-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-5894: - Attachment: PHOENIX-5894.patch > Table versus Table Full Outer join on Salted tables not working > --- > > Key: PHOENIX-5894 > URL: https://issues.apache.org/jira/browse/PHOENIX-5894 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.0.0 >Reporter: Ben Cohen >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5894.patch, PHOENIX-5894.patch, > Salt_Bucketed_Table_Full_Outer_Join_Issue.docx > > > Trying to do a Full Outer Join on two tables. The operation works when the > tables are not salted but fails with an exception related to casting when > performed on the salted versions of the tables. Here is the exceptions: > "java.lang.ClassCastException: org.apache.phoenix.schema.PColumnImpl cannot > be cast to org.apache.phoenix.schema.ProjectedColumn > at > org.apache.phoenix.compile.JoinCompiler.joinProjectedTables(JoinCompiler.java:1256) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:425) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:228) > at > org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:191) > at > org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:153) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:490) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:456) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:302) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:291) > at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:290) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:283) > at > org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1830) > at sqlline.Commands.execute(Commands.java:822) > at sqlline.Commands.sql(Commands.java:732) > at sqlline.SqlLine.dispatch(SqlLine.java:813) > at sqlline.SqlLine.begin(SqlLine.java:686) > at sqlline.SqlLine.start(SqlLine.java:398) > at sqlline.SqlLine.main(SqlLine.java:291)" > I have attached a word document with the complete list of queries and their > results, along with commands to recreate the data. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5894) Table versus Table Full Outer join on Salted tables not working
[ https://issues.apache.org/jira/browse/PHOENIX-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-5894: - Attachment: PHOENIX-5894.patch > Table versus Table Full Outer join on Salted tables not working > --- > > Key: PHOENIX-5894 > URL: https://issues.apache.org/jira/browse/PHOENIX-5894 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.0.0 >Reporter: Ben Cohen >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Attachments: PHOENIX-5894.patch, > Salt_Bucketed_Table_Full_Outer_Join_Issue.docx > > > Trying to do a Full Outer Join on two tables. The operation works when the > tables are not salted but fails with an exception related to casting when > performed on the salted versions of the tables. Here is the exceptions: > "java.lang.ClassCastException: org.apache.phoenix.schema.PColumnImpl cannot > be cast to org.apache.phoenix.schema.ProjectedColumn > at > org.apache.phoenix.compile.JoinCompiler.joinProjectedTables(JoinCompiler.java:1256) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:425) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:228) > at > org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:191) > at > org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:153) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:490) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:456) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:302) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:291) > at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:290) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:283) > at > org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1830) > at sqlline.Commands.execute(Commands.java:822) > at sqlline.Commands.sql(Commands.java:732) > at sqlline.SqlLine.dispatch(SqlLine.java:813) > at sqlline.SqlLine.begin(SqlLine.java:686) > at sqlline.SqlLine.start(SqlLine.java:398) > at sqlline.SqlLine.main(SqlLine.java:291)" > I have attached a word document with the complete list of queries and their > results, along with commands to recreate the data. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5846) Let the python client parse options from the JDBC URL
[ https://issues.apache.org/jira/browse/PHOENIX-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5846. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed Included in commit for PHOENIX-5880 > Let the python client parse options from the JDBC URL > - > > Key: PHOENIX-5846 > URL: https://issues.apache.org/jira/browse/PHOENIX-5846 > Project: Phoenix > Issue Type: Sub-task > Components: queryserver >Reporter: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > > It would be nice if the Python client could use and parse the same URL format > as the JDBC client, at least for the supported options. > If it doesn't fit into the python DB model, then provide a utility function > for it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5846) Let the python client parse options from the JDBC URL
[ https://issues.apache.org/jira/browse/PHOENIX-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-5846: Assignee: Istvan Toth > Let the python client parse options from the JDBC URL > - > > Key: PHOENIX-5846 > URL: https://issues.apache.org/jira/browse/PHOENIX-5846 > Project: Phoenix > Issue Type: Sub-task > Components: queryserver >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > > It would be nice if the Python client could use and parse the same URL format > as the JDBC client, at least for the supported options. > If it doesn't fit into the python DB model, then provide a utility function > for it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5844) Feature parity for the python client
[ https://issues.apache.org/jira/browse/PHOENIX-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5844. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed > Feature parity for the python client > > > Key: PHOENIX-5844 > URL: https://issues.apache.org/jira/browse/PHOENIX-5844 > Project: Phoenix > Issue Type: Improvement >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > We are shipping a python client for PQS, but it is out of date, and does not > have feature parity with the Java thin client. > This is an umbrella ticket to track the various sub-tasks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5880) Add SQLAchemy support to python driver
[ https://issues.apache.org/jira/browse/PHOENIX-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5880. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed > Add SQLAchemy support to python driver > -- > > Key: PHOENIX-5880 > URL: https://issues.apache.org/jira/browse/PHOENIX-5880 > Project: Phoenix > Issue Type: New Feature > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > > The pyphoenix project includes a an SqlAlchemy driver, we should adopt it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v5.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch, PHOENIX-5831.master.v3.patch, > PHOENIX-5831.master.v4.patch, PHOENIX-5831.master.v5.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.4.x.v4.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.4.x.v4.patch, > PHOENIX-5656.master.v1.patch, PHOENIX-5656.master.v2.patch, > PHOENIX-5656.master.v3.patch, PHOENIX-5656.master.v4.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.master.v4.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5656.master.v4.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5891) Ensure that code coverage does not drop with subsequent commits
[ https://issues.apache.org/jira/browse/PHOENIX-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5891: -- Attachment: (was: PHOENIX-5891-master-v1.patch) > Ensure that code coverage does not drop with subsequent commits > --- > > Key: PHOENIX-5891 > URL: https://issues.apache.org/jira/browse/PHOENIX-5891 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Assignee: Chinmay Kulkarni >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5891-master-v1.patch > > > With [PHOENIX-5842|https://issues.apache.org/jira/browse/PHOENIX-5842], we > added Jacoco code coverage to Hadoop QA precommit runs. We should add a check > to test-patch.sh to ensure that the code coverage numbers do not drop when > applying a new patch. > This can also check that overall code coverage is above a fixed threshold as > well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5891) Ensure that code coverage does not drop with subsequent commits
[ https://issues.apache.org/jira/browse/PHOENIX-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5891: -- Attachment: PHOENIX-5891-master-v1.patch > Ensure that code coverage does not drop with subsequent commits > --- > > Key: PHOENIX-5891 > URL: https://issues.apache.org/jira/browse/PHOENIX-5891 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Assignee: Chinmay Kulkarni >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5891-master-v1.patch > > > With [PHOENIX-5842|https://issues.apache.org/jira/browse/PHOENIX-5842], we > added Jacoco code coverage to Hadoop QA precommit runs. We should add a check > to test-patch.sh to ensure that the code coverage numbers do not drop when > applying a new patch. > This can also check that overall code coverage is above a fixed threshold as > well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
