[jira] [Updated] (PHOENIX-5919) Add tests and improve code coverage in PhoenixConnection
[ https://issues.apache.org/jira/browse/PHOENIX-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5919: -- Description: Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Add tests and improve code coverage in PhoenixConnection > > > Key: PHOENIX-5919 > URL: https://issues.apache.org/jira/browse/PHOENIX-5919 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > Please take a look at the latest build for the latest code coverage. We > should aim at at least 75% coverage. > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5918) Add testing and improve code coverage for PhoenixResultSet
[ https://issues.apache.org/jira/browse/PHOENIX-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5918: -- Description: Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Add testing and improve code coverage for PhoenixResultSet > -- > > Key: PHOENIX-5918 > URL: https://issues.apache.org/jira/browse/PHOENIX-5918 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > Please take a look at the latest build for the latest code coverage. We > should aim at at least 75% coverage. > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5917) Refactor ConnectionQueryServicesImpl and add more testing
[ https://issues.apache.org/jira/browse/PHOENIX-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5917: -- Description: Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Refactor ConnectionQueryServicesImpl and add more testing > - > > Key: PHOENIX-5917 > URL: https://issues.apache.org/jira/browse/PHOENIX-5917 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > Please take a look at the latest build for the latest code coverage. We > should aim at at least 75% coverage. > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5914) Add tests for UpgradeUtil and improve code coverage
[ https://issues.apache.org/jira/browse/PHOENIX-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5914: -- Description: We lack testing in this class and should refactor and add unit + integration tests. Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:We lack testing in this class and should refactor and add unit + integration tests. Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Add tests for UpgradeUtil and improve code coverage > --- > > Key: PHOENIX-5914 > URL: https://issues.apache.org/jira/browse/PHOENIX-5914 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > We lack testing in this class and should refactor and add unit + integration > tests. Please take a look at the latest build for the latest code coverage. > We should aim at at least 75% coverage. > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5916) Add testing and improve code coverage for ClientRpcControllerFactory and ServerRpcControllerFactory
[ https://issues.apache.org/jira/browse/PHOENIX-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5916: -- Description: Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Add testing and improve code coverage for ClientRpcControllerFactory and > ServerRpcControllerFactory > --- > > Key: PHOENIX-5916 > URL: https://issues.apache.org/jira/browse/PHOENIX-5916 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > Please take a look at the latest build for the latest code coverage. We > should aim at at least 75% coverage. > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5915) Improve code coverage in the 'org.apache.phoenix.util' package
[ https://issues.apache.org/jira/browse/PHOENIX-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5915: -- Description: Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Improve code coverage in the 'org.apache.phoenix.util' package > -- > > Key: PHOENIX-5915 > URL: https://issues.apache.org/jira/browse/PHOENIX-5915 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > Please take a look at the latest build for the latest code coverage. We > should aim at at least 75% coverage. > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5912) Improve code coverage for the 'org.apache.phoenix.coprocessor.tasks' package
[ https://issues.apache.org/jira/browse/PHOENIX-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5912: -- Description: Currently the instruction code coverage for this package is 42% and branch coverage is 25%. Please see any latest build to confirm the code paths that are uncovered in testing. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:Currently the instruction code coverage for this package is 42% and branch coverage is 25%. Please see any latest build to confirm the code paths that are uncovered in testing. > Improve code coverage for the 'org.apache.phoenix.coprocessor.tasks' package > > > Key: PHOENIX-5912 > URL: https://issues.apache.org/jira/browse/PHOENIX-5912 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > Currently the instruction code coverage for this package is 42% and branch > coverage is 25%. Please see any latest build to confirm the code paths that > are uncovered in testing. > > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5913) Improve code coverage for the 'org.apache.phoenix.job' package
[ https://issues.apache.org/jira/browse/PHOENIX-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5913: -- Description: We especially need to add tests for AbstraceRoundRobinQueue and JobManager. Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. Sample build : [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] was:We especially need to add tests for AbstraceRoundRobinQueue and JobManager. Please take a look at the latest build for the latest code coverage. We should aim at at least 75% coverage. > Improve code coverage for the 'org.apache.phoenix.job' package > -- > > Key: PHOENIX-5913 > URL: https://issues.apache.org/jira/browse/PHOENIX-5913 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > > We especially need to add tests for AbstraceRoundRobinQueue and JobManager. > Please take a look at the latest build for the latest code coverage. We > should aim at at least 75% coverage. > > Sample build : > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3873/artifact/phoenix-core/target/site/jacoco/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842_addendum.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.4.x.patch, > PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5892) Add code coverage steps in build documentation
[ https://issues.apache.org/jira/browse/PHOENIX-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5892: -- Attachment: PHOENIX-5892.master.v1.patch > Add code coverage steps in build documentation > -- > > Key: PHOENIX-5892 > URL: https://issues.apache.org/jira/browse/PHOENIX-5892 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5892.4.x.v1.patch, PHOENIX-5892.master.v1.patch > > > We need to add the steps for code coverage feature as part of build > documentation. The feature is introduced as part of PHOENIX-5842 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5893) Code coverage report not generated sometimes because of malformed input
Sandeep Guggilam created PHOENIX-5893:
-
Summary: Code coverage report not generated sometimes because of
malformed input
Key: PHOENIX-5893
URL: https://issues.apache.org/jira/browse/PHOENIX-5893
Project: Phoenix
Issue Type: Bug
Reporter: Sandeep Guggilam
Sometimes the code coverage report is not generated because of error "malformed
input around byte 2" . Have seen this mainly for builds that are very slow in
execution especially from the master branch
This could happen because of the VM getting terminated quickly before Jacoco
would write the results to Jacoco.exec file. May be explore setting the below
property to a value greater than default of 30 sec for VM to terminate
{{forkedProcessExitTimeoutInSeconds}}
{{}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5892) Add code coverage steps in build documentation
[ https://issues.apache.org/jira/browse/PHOENIX-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5892: -- Attachment: PHOENIX-5892.4.x.v1.patch > Add code coverage steps in build documentation > -- > > Key: PHOENIX-5892 > URL: https://issues.apache.org/jira/browse/PHOENIX-5892 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5892.4.x.v1.patch > > > We need to add the steps for code coverage feature as part of build > documentation. The feature is introduced as part of PHOENIX-5842 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842_addendum.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.4.x.patch, > PHOENIX-5842_addendum.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5892) Add code coverage steps in build documentation
Sandeep Guggilam created PHOENIX-5892: - Summary: Add code coverage steps in build documentation Key: PHOENIX-5892 URL: https://issues.apache.org/jira/browse/PHOENIX-5892 Project: Phoenix Issue Type: Improvement Reporter: Sandeep Guggilam Assignee: Sandeep Guggilam We need to add the steps for code coverage feature as part of build documentation. The feature is introduced as part of PHOENIX-5842 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842_addendum.4.x.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.4.x.patch, > PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842_addendum.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842_addendum.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842_addendum.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842_addendum.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842_addendum.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842_addendum.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842_addendum.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch, PHOENIX-5842_addendum.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.master.v1.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch, > PHOENIX-5842.master.v1.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v2.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842.4.x.v2.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v2.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842.4.x.v2.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v2.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842.4.x.v2.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v2.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842.4.x.v2.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v2.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: (was: PHOENIX-5842.4.x.v2.patch) > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v2.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch, PHOENIX-5842.4.x.v2.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5580:
--
Attachment: PHOENIX-5580.master.v1.patch
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5580.4.x.v1.patch, PHOENIX-5580.4.x.v2.patch,
> PHOENIX-5580.4.x.v3.patch, PHOENIX-5580.master.v1.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5580:
--
Attachment: (was: PHOENIX-5580.master.v1.patch)
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5580.4.x.v1.patch, PHOENIX-5580.4.x.v2.patch,
> PHOENIX-5580.4.x.v3.patch, PHOENIX-5580.master.v1.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5842: -- Attachment: PHOENIX-5842.4.x.v1.patch > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > Attachments: PHOENIX-5842.4.x.v1.patch > > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5580:
--
Attachment: PHOENIX-5580.master.v1.patch
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5580.4.x.v1.patch, PHOENIX-5580.4.x.v2.patch,
> PHOENIX-5580.4.x.v3.patch, PHOENIX-5580.master.v1.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5580:
--
Attachment: PHOENIX-5580.4.x.v3.patch
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5580.4.x.v1.patch, PHOENIX-5580.4.x.v2.patch,
> PHOENIX-5580.4.x.v3.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
[ https://issues.apache.org/jira/browse/PHOENIX-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5863: -- Attachment: PHOENIX-5863.4.x.v1.patch > Upsert into view against a table with index throws exception when 4.14.3 > client connects to 4.16 server > --- > > Key: PHOENIX-5863 > URL: https://issues.apache.org/jira/browse/PHOENIX-5863 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Blocker > Attachments: PHOENIX-5863.4.x.v1.patch > > > Steps to reproduce: > # Bring up a 4.16 server ( current 4.x branch) > # Connect a 4.14.3 client to the server and execute below queries > # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 > VARCHAR(10)); > # CREATE INDEX T1_IDX ON T1(V1); > # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; > # UPSERT INTO T1_V1(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below > exception*** > *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: > Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one > index write failed after retries,serverTimestamp=1587513404084,* > *at > org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* > *at > org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* > *at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* > *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* > *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* > *Caused by: > org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: > disableIndexOnFailure=false, Failed to write to multiple index tables: > [V2#I2|#I2]* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* > *... 21 more* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5877) Add indexing support in backward compat test framework
Sandeep Guggilam created PHOENIX-5877: - Summary: Add indexing support in backward compat test framework Key: PHOENIX-5877 URL: https://issues.apache.org/jira/browse/PHOENIX-5877 Project: Phoenix Issue Type: Improvement Reporter: Sandeep Guggilam We need to add the indexing support as part of backward compatibility test framework introduced as part of PHOENIX-5607 to catch any indexing related bugs when old client connects to the updated server -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
[ https://issues.apache.org/jira/browse/PHOENIX-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam reassigned PHOENIX-5863: - Assignee: Sandeep Guggilam > Upsert into view against a table with index throws exception when 4.14.3 > client connects to 4.16 server > --- > > Key: PHOENIX-5863 > URL: https://issues.apache.org/jira/browse/PHOENIX-5863 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Blocker > > Steps to reproduce: > # Bring up a 4.16 server ( current 4.x branch) > # Connect a 4.14.3 client to the server and execute below queries > # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 > VARCHAR(10)); > # CREATE INDEX T1_IDX ON T1(V1); > # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; > # UPSERT INTO T1_V1(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below > exception*** > *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: > Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one > index write failed after retries,serverTimestamp=1587513404084,* > *at > org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* > *at > org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* > *at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* > *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* > *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* > *Caused by: > org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: > disableIndexOnFailure=false, Failed to write to multiple index tables: > [V2#I2|#I2]* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* > *... 21 more* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5260) Create new documentation page for UpdateStatisticsTool usage and options
[ https://issues.apache.org/jira/browse/PHOENIX-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5260: -- Labels: (was: phoenix-hardening) > Create new documentation page for UpdateStatisticsTool usage and options > > > Key: PHOENIX-5260 > URL: https://issues.apache.org/jira/browse/PHOENIX-5260 > Project: Phoenix > Issue Type: Improvement >Reporter: Karan Mehta >Assignee: Xinyi Yan >Priority: Major > > FYI [~yanxinyi] > It will be good to add this for new users before the release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5805) Verify GlobalClientMetric values and add more testing around various metrics
[ https://issues.apache.org/jira/browse/PHOENIX-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5805: -- Priority: Major (was: Blocker) > Verify GlobalClientMetric values and add more testing around various metrics > > > Key: PHOENIX-5805 > URL: https://issues.apache.org/jira/browse/PHOENIX-5805 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Chinmay Kulkarni >Priority: Major > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > > We have seen situations where Phoenix GlobalClientMetrics show up with zero > values (for ex, 'tq') and no tests catch this. This Jira is to track efforts > to verify metric values are being updated correctly and add more rigorous > testing around the same. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
[ https://issues.apache.org/jira/browse/PHOENIX-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5863: -- Description: Steps to reproduce: # Bring up a 4.16 server ( current 4.x branch) # Connect a 4.14.3 client to the server and execute below queries # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 VARCHAR(10)); # CREATE INDEX T1_IDX ON T1(V1); # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; # UPSERT INTO T1_V1(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below exception*** *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one index write failed after retries,serverTimestamp=1587513404084,* *at org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* *at org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* *at org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* *at org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* *at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* *at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* *at org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* *at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* *at org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* *at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* *Caused by: org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: disableIndexOnFailure=false, Failed to write to multiple index tables: [V2#I2|#I2]* *at org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* *... 21 more* was: Steps to reproduce: # Bring up a 4.16 server ( current 4.x branch) # Connect a 4.14.3 client to the server and execute below queries # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 VARCHAR(10)); # CREATE INDEX T1_IDX ON T1(V1); # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; # UPSERT INTO T2_V2(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below exception*** *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one index write failed after retries,serverTimestamp=1587513404084,* *at org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* *at org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* *at org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* *at org.apache.hadoop.hbase.regionserver.R
[jira] [Created] (PHOENIX-5864) RuleGeneratorTest unit test seem to be failing
Sandeep Guggilam created PHOENIX-5864: - Summary: RuleGeneratorTest unit test seem to be failing Key: PHOENIX-5864 URL: https://issues.apache.org/jira/browse/PHOENIX-5864 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.0 Reporter: Sandeep Guggilam Looks to be related to this commit : [https://github.com/apache/phoenix/commit/8ee78e2be4858f3ed230dff2328269ebe67e1f03] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
Sandeep Guggilam created PHOENIX-5863: - Summary: Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server Key: PHOENIX-5863 URL: https://issues.apache.org/jira/browse/PHOENIX-5863 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.0 Reporter: Sandeep Guggilam Steps to reproduce: # Bring up a 4.16 server ( current 4.x branch) # Connect a 4.14.3 client to the server and execute below queries # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 VARCHAR(10)); # CREATE INDEX T1_IDX ON T1(V1); # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; # UPSERT INTO T2_V2(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below exception*** *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one index write failed after retries,serverTimestamp=1587513404084,* *at org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* *at org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* *at org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* *at org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* *at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* *at org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* *at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* *at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* *at org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* *at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* *at org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* *at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* *Caused by: org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: disableIndexOnFailure=false, Failed to write to multiple index tables: [V2#I2]* *at org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* *... 21 more* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5842) Code Coverage tool for Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam reassigned PHOENIX-5842: - Assignee: Sandeep Guggilam > Code Coverage tool for Phoenix > -- > > Key: PHOENIX-5842 > URL: https://issues.apache.org/jira/browse/PHOENIX-5842 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Labels: quality-improvement > > Currently we don't have any code coverage tool for Phoenix. This is required > for us to measure the test coverage and helps us in improving the test suite > further till we reach may be 80% coverage > The test coverage results can also be integrated into the Hadoop QA run of > the precommit build such that the reviewers could take a look at the report > and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5580:
--
Attachment: PHOENIX-5580.4.x.v2.patch
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5580.4.x.v1.patch, PHOENIX-5580.4.x.v2.patch
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5580:
--
Attachment: PHOENIX-5580.4.x.v1.patch
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5580.4.x.v1.patch
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-5842) Code Coverage tool for Phoenix
Sandeep Guggilam created PHOENIX-5842: - Summary: Code Coverage tool for Phoenix Key: PHOENIX-5842 URL: https://issues.apache.org/jira/browse/PHOENIX-5842 Project: Phoenix Issue Type: Improvement Reporter: Sandeep Guggilam Currently we don't have any code coverage tool for Phoenix. This is required for us to measure the test coverage and helps us in improving the test suite further till we reach may be 80% coverage The test coverage results can also be integrated into the Hadoop QA run of the precommit build such that the reviewers could take a look at the report and see if the added code doesn't have enough coverage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam reassigned PHOENIX-5580:
-
Assignee: Sandeep Guggilam (was: Abhishek Singh Chouhan)
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.master.v2.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.4.x.v1.patch, PHOENIX-5718.master.v1.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.master.v2.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.4.x.v1.patch, PHOENIX-5718.master.v1.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.4.x.v1.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.4.x.v1.patch, PHOENIX-5718.master.v1.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.master.v2.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.4.x.v1.patch, PHOENIX-5718.master.v1.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5746) Update release documentation to include versions information
[ https://issues.apache.org/jira/browse/PHOENIX-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5746: -- Attachment: PHOENIX-5746.v2.patch > Update release documentation to include versions information > > > Key: PHOENIX-5746 > URL: https://issues.apache.org/jira/browse/PHOENIX-5746 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5746.patch, PHOENIX-5746.v2.patch > > > We need to update the release documentation to update the VERSIONS > information that include current version ( major or minor or patch version > change) and the compatible client versions with the current version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5790) Add Apache license header to compatible_client_versions.json
[ https://issues.apache.org/jira/browse/PHOENIX-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5790: -- Attachment: PHOENIX-5790.master.v1.patch > Add Apache license header to compatible_client_versions.json > > > Key: PHOENIX-5790 > URL: https://issues.apache.org/jira/browse/PHOENIX-5790 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0, 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Minor > Attachments: PHOENIX-5790.4.x.v1.patch, PHOENIX-5790.master.v1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5790) Add Apache license header to compatible_client_versions.json
[ https://issues.apache.org/jira/browse/PHOENIX-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5790: -- Attachment: PHOENIX-5790.4.x.v1.patch > Add Apache license header to compatible_client_versions.json > > > Key: PHOENIX-5790 > URL: https://issues.apache.org/jira/browse/PHOENIX-5790 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0, 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Minor > Attachments: PHOENIX-5790.4.x.v1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5790) Add Apache license header to compatible_client_versions.json
Sandeep Guggilam created PHOENIX-5790: - Summary: Add Apache license header to compatible_client_versions.json Key: PHOENIX-5790 URL: https://issues.apache.org/jira/browse/PHOENIX-5790 Project: Phoenix Issue Type: Bug Affects Versions: 5.1.0, 4.16.0 Reporter: Sandeep Guggilam Assignee: Sandeep Guggilam -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5746) Update release documentation to include versions information
[ https://issues.apache.org/jira/browse/PHOENIX-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5746: -- Attachment: (was: PHOENIX-5746.master.v1.patch) > Update release documentation to include versions information > > > Key: PHOENIX-5746 > URL: https://issues.apache.org/jira/browse/PHOENIX-5746 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5746.patch > > > We need to update the release documentation to update the VERSIONS > information that include current version ( major or minor or patch version > change) and the compatible client versions with the current version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5746) Update release documentation to include versions information
[ https://issues.apache.org/jira/browse/PHOENIX-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5746: -- Attachment: PHOENIX-5746.patch > Update release documentation to include versions information > > > Key: PHOENIX-5746 > URL: https://issues.apache.org/jira/browse/PHOENIX-5746 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5746.patch > > > We need to update the release documentation to update the VERSIONS > information that include current version ( major or minor or patch version > change) and the compatible client versions with the current version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5746) Update release documentation to include versions information
[ https://issues.apache.org/jira/browse/PHOENIX-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5746: -- Attachment: PHOENIX-5746.master.v1.patch > Update release documentation to include versions information > > > Key: PHOENIX-5746 > URL: https://issues.apache.org/jira/browse/PHOENIX-5746 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5746.master.v1.patch > > > We need to update the release documentation to update the VERSIONS > information that include current version ( major or minor or patch version > change) and the compatible client versions with the current version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.master.v2.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch, > PHOENIX-5607.master.v2.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.master.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch, > PHOENIX-5607.master.v2.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.master.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch, > PHOENIX-5607.master.v2.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.master.v2.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.master.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch, > PHOENIX-5607.master.v2.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.master.v2.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.master.v2.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.master.v2.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.master.v2.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5779) SpliitSystemCatalogIT tests fail with Multiple Regions error
Sandeep Guggilam created PHOENIX-5779: - Summary: SpliitSystemCatalogIT tests fail with Multiple Regions error Key: PHOENIX-5779 URL: https://issues.apache.org/jira/browse/PHOENIX-5779 Project: Phoenix Issue Type: Bug Affects Versions: 5.1.0 Reporter: Sandeep Guggilam I see the SplitSystemCatalogIT tests failing on master branch complaining with the error " Multiple regions on server" when it tries to split the system catalog. Sample builds where it failed: [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3560//testReport/] [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3571//testReport/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.master.v2.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.master.v2.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5776) Phoenix pherf unit tests failing
[ https://issues.apache.org/jira/browse/PHOENIX-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5776: -- Attachment: PHOENIX-5776.master.v1.patch > Phoenix pherf unit tests failing > > > Key: PHOENIX-5776 > URL: https://issues.apache.org/jira/browse/PHOENIX-5776 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0, 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Attachments: PHOENIX-5776.master.v1.patch > > > Phoenix Pherf unit tests ResourceTest and PherfTest are failing with "could > not load resources /datamodel/query_more.sql" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5776) Phoenix pherf unit tests failing
Sandeep Guggilam created PHOENIX-5776: - Summary: Phoenix pherf unit tests failing Key: PHOENIX-5776 URL: https://issues.apache.org/jira/browse/PHOENIX-5776 Project: Phoenix Issue Type: Bug Affects Versions: 5.1.0, 4.16.0 Reporter: Sandeep Guggilam Assignee: Sandeep Guggilam Phoenix Pherf unit tests ResourceTest and PherfTest are failing with "could not load resources /datamodel/query_more.sql" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5317) Upserting rows into child views with pk fails when the base view has an index on it.
[
https://issues.apache.org/jira/browse/PHOENIX-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5317:
--
Attachment: PHOENIX-5317.master.v1.patch
> Upserting rows into child views with pk fails when the base view has an index
> on it.
>
>
> Key: PHOENIX-5317
> URL: https://issues.apache.org/jira/browse/PHOENIX-5317
> Project: Phoenix
> Issue Type: Sub-task
>Affects Versions: 4.13.0, 4.14.1
>Reporter: Jacob Isaac
>Assignee: Sandeep Guggilam
>Priority: Major
> Attachments: PHOENIX-5137-TestFailure.txt,
> PHOENIX-5317.4.x-HBase-1.3.v1.patch, PHOENIX-5317.4.x-HBase-1.3.v2.patch,
> PHOENIX-5317.4.x-HBase-1.3.v3.patch, PHOENIX-5317.master.v1.patch
>
>
> Steps to reproduce -
> 1 Create Base Table, Base/Global View and Index using non tenanted connection.
> CREATE TABLE IF NOT EXISTS TEST.BASETABLE (
> TENANT_ID CHAR(15) NOT NULL,
> KEY_PREFIX CHAR(3) NOT NULL,
> CREATED_DATE DATE,
> CREATED_BY CHAR(15),
> SYSTEM_MODSTAMP DATE
> CONSTRAINT PK PRIMARY KEY (
> TENANT_ID,
> KEY_PREFIX
> )
> ) VERSIONS=1, MULTI_TENANT=true, IMMUTABLE_ROWS=TRUE, REPLICATION_SCOPE=1;
> CREATE VIEW IF NOT EXISTS TEST.MY_GLOBAL_VIEW (
> TEXT1 VARCHAR NOT NULL,
> INT1 BIGINT NOT NULL,
> DOUBLE1 DECIMAL(12, 3),
> IS_BOOLEAN BOOLEAN,
> RELATIONSHIP_ID CHAR(15),
> TEXT_READ_ONLY VARCHAR,
> DATE_TIME1 DATE,
> JSON1 VARCHAR,
> IP_START_ADDRESS VARCHAR
> CONSTRAINT PKVIEW PRIMARY KEY
> (
> TEXT1, INT1
> )
> )
> AS SELECT * FROM TEST.BASETABLE WHERE KEY_PREFIX = '0CY';
> CREATE INDEX IF NOT EXISTS TEST_MY_GLOBAL_VIEW_SEC_INDEX
> ON TEST.MY_GLOBAL_VIEW (TEXT1, INT1)
> INCLUDE (CREATED_BY, RELATIONSHIP_ID, JSON1, DOUBLE1, IS_BOOLEAN,
> IP_START_ADDRESS, CREATED_DATE, SYSTEM_MODSTAMP, TEXT_READ_ONLY);
> 2. Create child view using an tenant-owned connection
> CREATE VIEW IF NOT EXISTS TEST."z01" (COL1 VARCHAR, COL2 VARCHAR, COL3
> VARCHAR, COL4 VARCHAR CONSTRAINT PK PRIMARY KEY (COL1, COL2, COL3, COL4)) AS
> SELECT * FROM TEST.MY_GLOBAL_VIEW;
> 3. Upsert into child view
> UPSERT INTO TEST."z01" (DATE_TIME1, INT1, TEXT1, COL1, COL2, COL3, COL4)
> VALUES (TO_DATE('2017-10-16 22:00:00', '-MM-dd HH:mm:ss'), 10, 'z',
> '8', 'z', 'z', 'z');
> Following exception is thrown -
> 0: jdbc:phoenix:localhost> UPSERT INTO TEST."z01" (DATE_TIME1, INT1, TEXT1,
> COL1, COL2, COL3, COL4) VALUES (TO_DATE('2017-10-16 22:00:00', '-MM-dd
> HH:mm:ss'), 10, 'z', '8', 'z', 'z', 'z');
> java.lang.IllegalArgumentException
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
> at
> com.google.common.collect.Lists.computeArrayListCapacity(Lists.java:105)
> at
> com.google.common.collect.Lists.newArrayListWithExpectedSize(Lists.java:195)
> at
> org.apache.phoenix.index.IndexMaintainer.(IndexMaintainer.java:424)
> at
> org.apache.phoenix.index.IndexMaintainer.create(IndexMaintainer.java:143)
> at
> org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(PTableImpl.java:1176)
> at
> org.apache.phoenix.util.IndexUtil.generateIndexData(IndexUtil.java:303)
> at
> org.apache.phoenix.execute.MutationState$1.next(MutationState.java:519)
> at
> org.apache.phoenix.execute.MutationState$1.next(MutationState.java:501)
> at org.apache.phoenix.execute.MutationState.send(MutationState.java:941)
> at
> org.apache.phoenix.execute.MutationState.send(MutationState.java:1387)
> at
> org.apache.phoenix.execute.MutationState.commit(MutationState.java:1228)
> at
> org.apache.phoenix.jdbc.PhoenixConnection$3.call(PhoenixConnection.java:666)
> at
> org.apache.phoenix.jdbc.PhoenixConnection$3.call(PhoenixConnection.java:662)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.commit(PhoenixConnection.java:662)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:399)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:379)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:366)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1775)
> at sqlline.Commands.execute(Commands.java:822)
> at sqlline.Commands.sql(Commands.java:732)
> at sqlline.SqlLine.dispatch(SqlLine.java:807)
> at sqlline.SqlLine.begin(SqlLine.java:681)
> at sqlline.SqlLine.start(SqlLine.java:398)
> at sqlline
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x.v1.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.4.x.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.4.x.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.4.x.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x.v1.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x.v1.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x.v1.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.4.x.v1.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.4.x.v1.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.4.x.v1.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.4.x.v1.patch, > PHOENIX-5718.master.v1.patch, PHOENIX-5718.master.v2.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.4.x.v1.patch, PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.4.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.5.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.4.x-HBase-1.4.v1.patch, PHOENIX-5607.4.x-HBase-1.5.v1.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.master.v2.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.master.v1.patch, > PHOENIX-5718.master.v2.patch, PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: PHOENIX-5718.master.v2.patch > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.master.v1.patch, > PHOENIX-5718.master.v2.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5718) GetTable builds a table excluding the given clientTimeStamp
[ https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5718: -- Attachment: (was: PHOENIX-5718.master.v2.patch) > GetTable builds a table excluding the given clientTimeStamp > --- > > Key: PHOENIX-5718 > URL: https://issues.apache.org/jira/browse/PHOENIX-5718 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch, > PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.master.v1.patch > > > Here is the scenario tested: > # Brought up a server with 4.16 where new columns are added but not added as > part of upgrade path > # Connect with 4.14 client > # Connect with a 4.16 client - this will throw an exception as the new > columns added as part of 4.16 were not added as part of upgrade path > # Now the code will force update the cache in > PhoenixStatement#executeQuery() method > # Now the buildTable is removing even the columns added as part of 4.15 , > the reason being we are passing the clientTimeStamp to build table ( say 29 > is the timestamp for column added for 4.15) but the table is scanning rows > EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes > the end time stamp > The passing of clientTimeStamp to build table is in > MetaDataEndPointImpl#doGetTable method -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5317) Upserting rows into child views with pk fails when the base view has an index on it.
[
https://issues.apache.org/jira/browse/PHOENIX-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5317:
--
Attachment: PHOENIX-5317.4.x-HBase-1.3.v3.patch
> Upserting rows into child views with pk fails when the base view has an index
> on it.
>
>
> Key: PHOENIX-5317
> URL: https://issues.apache.org/jira/browse/PHOENIX-5317
> Project: Phoenix
> Issue Type: Sub-task
>Affects Versions: 4.13.0, 4.14.1
>Reporter: Jacob Isaac
>Assignee: Sandeep Guggilam
>Priority: Major
> Attachments: PHOENIX-5137-TestFailure.txt,
> PHOENIX-5317.4.x-HBase-1.3.v1.patch, PHOENIX-5317.4.x-HBase-1.3.v2.patch,
> PHOENIX-5317.4.x-HBase-1.3.v3.patch
>
>
> Steps to reproduce -
> 1 Create Base Table, Base/Global View and Index using non tenanted connection.
> CREATE TABLE IF NOT EXISTS TEST.BASETABLE (
> TENANT_ID CHAR(15) NOT NULL,
> KEY_PREFIX CHAR(3) NOT NULL,
> CREATED_DATE DATE,
> CREATED_BY CHAR(15),
> SYSTEM_MODSTAMP DATE
> CONSTRAINT PK PRIMARY KEY (
> TENANT_ID,
> KEY_PREFIX
> )
> ) VERSIONS=1, MULTI_TENANT=true, IMMUTABLE_ROWS=TRUE, REPLICATION_SCOPE=1;
> CREATE VIEW IF NOT EXISTS TEST.MY_GLOBAL_VIEW (
> TEXT1 VARCHAR NOT NULL,
> INT1 BIGINT NOT NULL,
> DOUBLE1 DECIMAL(12, 3),
> IS_BOOLEAN BOOLEAN,
> RELATIONSHIP_ID CHAR(15),
> TEXT_READ_ONLY VARCHAR,
> DATE_TIME1 DATE,
> JSON1 VARCHAR,
> IP_START_ADDRESS VARCHAR
> CONSTRAINT PKVIEW PRIMARY KEY
> (
> TEXT1, INT1
> )
> )
> AS SELECT * FROM TEST.BASETABLE WHERE KEY_PREFIX = '0CY';
> CREATE INDEX IF NOT EXISTS TEST_MY_GLOBAL_VIEW_SEC_INDEX
> ON TEST.MY_GLOBAL_VIEW (TEXT1, INT1)
> INCLUDE (CREATED_BY, RELATIONSHIP_ID, JSON1, DOUBLE1, IS_BOOLEAN,
> IP_START_ADDRESS, CREATED_DATE, SYSTEM_MODSTAMP, TEXT_READ_ONLY);
> 2. Create child view using an tenant-owned connection
> CREATE VIEW IF NOT EXISTS TEST."z01" (COL1 VARCHAR, COL2 VARCHAR, COL3
> VARCHAR, COL4 VARCHAR CONSTRAINT PK PRIMARY KEY (COL1, COL2, COL3, COL4)) AS
> SELECT * FROM TEST.MY_GLOBAL_VIEW;
> 3. Upsert into child view
> UPSERT INTO TEST."z01" (DATE_TIME1, INT1, TEXT1, COL1, COL2, COL3, COL4)
> VALUES (TO_DATE('2017-10-16 22:00:00', '-MM-dd HH:mm:ss'), 10, 'z',
> '8', 'z', 'z', 'z');
> Following exception is thrown -
> 0: jdbc:phoenix:localhost> UPSERT INTO TEST."z01" (DATE_TIME1, INT1, TEXT1,
> COL1, COL2, COL3, COL4) VALUES (TO_DATE('2017-10-16 22:00:00', '-MM-dd
> HH:mm:ss'), 10, 'z', '8', 'z', 'z', 'z');
> java.lang.IllegalArgumentException
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
> at
> com.google.common.collect.Lists.computeArrayListCapacity(Lists.java:105)
> at
> com.google.common.collect.Lists.newArrayListWithExpectedSize(Lists.java:195)
> at
> org.apache.phoenix.index.IndexMaintainer.(IndexMaintainer.java:424)
> at
> org.apache.phoenix.index.IndexMaintainer.create(IndexMaintainer.java:143)
> at
> org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(PTableImpl.java:1176)
> at
> org.apache.phoenix.util.IndexUtil.generateIndexData(IndexUtil.java:303)
> at
> org.apache.phoenix.execute.MutationState$1.next(MutationState.java:519)
> at
> org.apache.phoenix.execute.MutationState$1.next(MutationState.java:501)
> at org.apache.phoenix.execute.MutationState.send(MutationState.java:941)
> at
> org.apache.phoenix.execute.MutationState.send(MutationState.java:1387)
> at
> org.apache.phoenix.execute.MutationState.commit(MutationState.java:1228)
> at
> org.apache.phoenix.jdbc.PhoenixConnection$3.call(PhoenixConnection.java:666)
> at
> org.apache.phoenix.jdbc.PhoenixConnection$3.call(PhoenixConnection.java:662)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.commit(PhoenixConnection.java:662)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:399)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:379)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:366)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1775)
> at sqlline.Commands.execute(Commands.java:822)
> at sqlline.Commands.sql(Commands.java:732)
> at sqlline.SqlLine.dispatch(SqlLine.java:807)
> at sqlline.SqlLine.begin(SqlLine.java:681)
> at sqlline.SqlLine.start(SqlLine.java:398)
> at sqlline.SqlLine.main(SqlLine.j
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.master.v1.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.master.v1.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch, > PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch, > PHOENIX-5607.master.v1.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5317) Upserting rows into child views with pk fails when the base view has an index on it.
[
https://issues.apache.org/jira/browse/PHOENIX-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Guggilam updated PHOENIX-5317:
--
Attachment: (was: PHOENIX-5317.4.x-HBase-1.3.v2.patch)
> Upserting rows into child views with pk fails when the base view has an index
> on it.
>
>
> Key: PHOENIX-5317
> URL: https://issues.apache.org/jira/browse/PHOENIX-5317
> Project: Phoenix
> Issue Type: Sub-task
>Affects Versions: 4.13.0, 4.14.1
>Reporter: Jacob Isaac
>Assignee: Sandeep Guggilam
>Priority: Major
> Attachments: PHOENIX-5137-TestFailure.txt,
> PHOENIX-5317.4.x-HBase-1.3.v1.patch, PHOENIX-5317.4.x-HBase-1.3.v2.patch
>
>
> Steps to reproduce -
> 1 Create Base Table, Base/Global View and Index using non tenanted connection.
> CREATE TABLE IF NOT EXISTS TEST.BASETABLE (
> TENANT_ID CHAR(15) NOT NULL,
> KEY_PREFIX CHAR(3) NOT NULL,
> CREATED_DATE DATE,
> CREATED_BY CHAR(15),
> SYSTEM_MODSTAMP DATE
> CONSTRAINT PK PRIMARY KEY (
> TENANT_ID,
> KEY_PREFIX
> )
> ) VERSIONS=1, MULTI_TENANT=true, IMMUTABLE_ROWS=TRUE, REPLICATION_SCOPE=1;
> CREATE VIEW IF NOT EXISTS TEST.MY_GLOBAL_VIEW (
> TEXT1 VARCHAR NOT NULL,
> INT1 BIGINT NOT NULL,
> DOUBLE1 DECIMAL(12, 3),
> IS_BOOLEAN BOOLEAN,
> RELATIONSHIP_ID CHAR(15),
> TEXT_READ_ONLY VARCHAR,
> DATE_TIME1 DATE,
> JSON1 VARCHAR,
> IP_START_ADDRESS VARCHAR
> CONSTRAINT PKVIEW PRIMARY KEY
> (
> TEXT1, INT1
> )
> )
> AS SELECT * FROM TEST.BASETABLE WHERE KEY_PREFIX = '0CY';
> CREATE INDEX IF NOT EXISTS TEST_MY_GLOBAL_VIEW_SEC_INDEX
> ON TEST.MY_GLOBAL_VIEW (TEXT1, INT1)
> INCLUDE (CREATED_BY, RELATIONSHIP_ID, JSON1, DOUBLE1, IS_BOOLEAN,
> IP_START_ADDRESS, CREATED_DATE, SYSTEM_MODSTAMP, TEXT_READ_ONLY);
> 2. Create child view using an tenant-owned connection
> CREATE VIEW IF NOT EXISTS TEST."z01" (COL1 VARCHAR, COL2 VARCHAR, COL3
> VARCHAR, COL4 VARCHAR CONSTRAINT PK PRIMARY KEY (COL1, COL2, COL3, COL4)) AS
> SELECT * FROM TEST.MY_GLOBAL_VIEW;
> 3. Upsert into child view
> UPSERT INTO TEST."z01" (DATE_TIME1, INT1, TEXT1, COL1, COL2, COL3, COL4)
> VALUES (TO_DATE('2017-10-16 22:00:00', '-MM-dd HH:mm:ss'), 10, 'z',
> '8', 'z', 'z', 'z');
> Following exception is thrown -
> 0: jdbc:phoenix:localhost> UPSERT INTO TEST."z01" (DATE_TIME1, INT1, TEXT1,
> COL1, COL2, COL3, COL4) VALUES (TO_DATE('2017-10-16 22:00:00', '-MM-dd
> HH:mm:ss'), 10, 'z', '8', 'z', 'z', 'z');
> java.lang.IllegalArgumentException
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
> at
> com.google.common.collect.Lists.computeArrayListCapacity(Lists.java:105)
> at
> com.google.common.collect.Lists.newArrayListWithExpectedSize(Lists.java:195)
> at
> org.apache.phoenix.index.IndexMaintainer.(IndexMaintainer.java:424)
> at
> org.apache.phoenix.index.IndexMaintainer.create(IndexMaintainer.java:143)
> at
> org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(PTableImpl.java:1176)
> at
> org.apache.phoenix.util.IndexUtil.generateIndexData(IndexUtil.java:303)
> at
> org.apache.phoenix.execute.MutationState$1.next(MutationState.java:519)
> at
> org.apache.phoenix.execute.MutationState$1.next(MutationState.java:501)
> at org.apache.phoenix.execute.MutationState.send(MutationState.java:941)
> at
> org.apache.phoenix.execute.MutationState.send(MutationState.java:1387)
> at
> org.apache.phoenix.execute.MutationState.commit(MutationState.java:1228)
> at
> org.apache.phoenix.jdbc.PhoenixConnection$3.call(PhoenixConnection.java:666)
> at
> org.apache.phoenix.jdbc.PhoenixConnection$3.call(PhoenixConnection.java:662)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.commit(PhoenixConnection.java:662)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:399)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:379)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:366)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1775)
> at sqlline.Commands.execute(Commands.java:822)
> at sqlline.Commands.sql(Commands.java:732)
> at sqlline.SqlLine.dispatch(SqlLine.java:807)
> at sqlline.SqlLine.begin(SqlLine.java:681)
> at sqlline.SqlLine.start(SqlLine.java:398)
> at sqlline.SqlLine.main(SqlLine.java:292)
--
This message w
