[jira] [Resolved] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

[ https://issues.apache.org/jira/browse/PHOENIX-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-4243. --- Resolution: Fixed Fix Version/s: 4.12.0 > Using rowtimestamp column with RVC causes

[jira] [Updated] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

[ https://issues.apache.org/jira/browse/PHOENIX-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-4243: -- Attachment: PHOENIX-4243_v2.patch Thanks for the reviews, James and Thomas. Will go ahead and

[jira] [Created] (PHOENIX-4254) PartialIndexRebuilderIT is flapping

James Taylor created PHOENIX-4254: - Summary: PartialIndexRebuilderIT is flapping Key: PHOENIX-4254 URL: https://issues.apache.org/jira/browse/PHOENIX-4254 Project: Phoenix Issue Type: Test

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185361#comment-16185361 ] Hudson commented on PHOENIX-4187: - FAILURE: Integrated in Jenkins build Phoenix-master #1819 (See

[jira] [Commented] (PHOENIX-4252) Remove BaseClientManagedTimeIT as it's no longer used

[ https://issues.apache.org/jira/browse/PHOENIX-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185360#comment-16185360 ] Hudson commented on PHOENIX-4252: - FAILURE: Integrated in Jenkins build Phoenix-master #1819 (See

[jira] [Resolved] (PHOENIX-4253) Make doSetup final to prevent errand overrides

[ https://issues.apache.org/jira/browse/PHOENIX-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4253. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Make

[jira] [Created] (PHOENIX-4253) Make doSetup final to prevent errand overrides

James Taylor created PHOENIX-4253: - Summary: Make doSetup final to prevent errand overrides Key: PHOENIX-4253 URL: https://issues.apache.org/jira/browse/PHOENIX-4253 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-4248) Breakup IndexExpressionIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4248: -- Attachment: PHOENIX-4248_addendum1.patch > Breakup IndexExpressionIT into several integration

[jira] [Commented] (PHOENIX-4238) MR IndexScrutinyTool break with salted tables and indexes on views

[ https://issues.apache.org/jira/browse/PHOENIX-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185308#comment-16185308 ] churro morales commented on PHOENIX-4238: - Yes I can get it for you tomorrow. The code works

[jira] [Commented] (PHOENIX-4251) Breakup ProductMetricsIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185301#comment-16185301 ] Hudson commented on PHOENIX-4251: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4249) Decrease unique name allocation for SequenceIT

[ https://issues.apache.org/jira/browse/PHOENIX-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185299#comment-16185299 ] Hudson commented on PHOENIX-4249: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4096) Disallow DML operations on connections with CURRENT_SCN set

[ https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185294#comment-16185294 ] Hudson commented on PHOENIX-4096: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4245) Breakup IndexIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185296#comment-16185296 ] Hudson commented on PHOENIX-4245: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4244) Breakup ArrayIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185295#comment-16185295 ] Hudson commented on PHOENIX-4244: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4246) Breakup join related tests into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185297#comment-16185297 ] Hudson commented on PHOENIX-4246: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4250) Breakup AlterTableIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185300#comment-16185300 ] Hudson commented on PHOENIX-4250: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Commented] (PHOENIX-4248) Breakup IndexExpressionIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185298#comment-16185298 ] Hudson commented on PHOENIX-4248: - FAILURE: Integrated in Jenkins build Phoenix-master #1818 (See

[jira] [Resolved] (PHOENIX-4244) Breakup ArrayIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4244. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Breakup

[jira] [Commented] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

[ https://issues.apache.org/jira/browse/PHOENIX-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185277#comment-16185277 ] Thomas D'Silva commented on PHOENIX-4243: - [~samarthjain] I had to comment out the same query on

[jira] [Commented] (PHOENIX-4238) MR IndexScrutinyTool break with salted tables and indexes on views

[ https://issues.apache.org/jira/browse/PHOENIX-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185276#comment-16185276 ] James Taylor commented on PHOENIX-4238: --- [~churromorales] - would it be possible to have a fix for

[jira] [Updated] (PHOENIX-4238) MR IndexScrutinyTool break with salted tables and indexes on views

[ https://issues.apache.org/jira/browse/PHOENIX-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4238: -- Summary: MR IndexScrutinyTool break with salted tables and indexes on views (was: Add

[jira] [Resolved] (PHOENIX-4246) Breakup join related tests into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4246. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Breakup

[jira] [Resolved] (PHOENIX-4249) Decrease unique name allocation for SequenceIT

[ https://issues.apache.org/jira/browse/PHOENIX-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4249. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Decrease

[jira] [Commented] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

[ https://issues.apache.org/jira/browse/PHOENIX-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185275#comment-16185275 ] James Taylor commented on PHOENIX-4243: --- +1. > Using rowtimestamp column with RVC causes an

[jira] [Resolved] (PHOENIX-4250) Breakup AlterTableIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4250. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Breakup

[jira] [Resolved] (PHOENIX-4251) Breakup ProductMetricsIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4251. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Breakup

[jira] [Resolved] (PHOENIX-4252) Remove BaseClientManagedTimeIT as it's no longer used

[ https://issues.apache.org/jira/browse/PHOENIX-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4252. --- Resolution: Fixed Assignee: James Taylor Fix Version/s: 4.12.0 > Remove

[jira] [Updated] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

[ https://issues.apache.org/jira/browse/PHOENIX-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-4243: -- Attachment: PHOENIX-4243.patch Patch that fixes the issue. Please review, [~jamestaylor]. >

[jira] [Assigned] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

[ https://issues.apache.org/jira/browse/PHOENIX-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reassigned PHOENIX-4243: - Assignee: Samarth Jain > Using rowtimestamp column with RVC causes an exception

[jira] [Resolved] (PHOENIX-4183) Disallow creating an index on a mutable table that has a row_timestamp column

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva resolved PHOENIX-4183. - Resolution: Fixed > Disallow creating an index on a mutable table that has a

[jira] [Updated] (PHOENIX-4252) Remove BaseClientManagedTimeIT as it's no longer used

[ https://issues.apache.org/jira/browse/PHOENIX-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4252: -- Attachment: PHOENIX-4252.patch > Remove BaseClientManagedTimeIT as it's no longer used >

[jira] [Updated] (PHOENIX-4252) Remove BaseClientManagedTimeIT as it's no longer used

[ https://issues.apache.org/jira/browse/PHOENIX-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4252: -- Summary: Remove BaseClientManagedTimeIT as it's no longer used (was: Remove

[jira] [Created] (PHOENIX-4252) Remove BaseClientTimeManagedIT as it's no longer used

James Taylor created PHOENIX-4252: - Summary: Remove BaseClientTimeManagedIT as it's no longer used Key: PHOENIX-4252 URL: https://issues.apache.org/jira/browse/PHOENIX-4252 Project: Phoenix

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185219#comment-16185219 ] Hudson commented on PHOENIX-4187: - FAILURE: Integrated in Jenkins build Phoenix-master #1817 (See

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185217#comment-16185217 ] Hadoop QA commented on PHOENIX-4187: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Created] (PHOENIX-4251) Breakup ProductMetricsIT into several integration tests so as not to create too many tables in one test

James Taylor created PHOENIX-4251: - Summary: Breakup ProductMetricsIT into several integration tests so as not to create too many tables in one test Key: PHOENIX-4251 URL:

[jira] [Commented] (PHOENIX-4219) Index gets out of sync on HBase 1.x

[ https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185178#comment-16185178 ] Vincent Poon commented on PHOENIX-4219: --- It seems to be a problem handling certain input. It's

[jira] [Created] (PHOENIX-4250) Breakup AlterTableIT into several integration tests so as not to create too many tables in one test

James Taylor created PHOENIX-4250: - Summary: Breakup AlterTableIT into several integration tests so as not to create too many tables in one test Key: PHOENIX-4250 URL:

[jira] [Created] (PHOENIX-4249) Decrease unique name allocation for SequenceIT

James Taylor created PHOENIX-4249: - Summary: Decrease unique name allocation for SequenceIT Key: PHOENIX-4249 URL: https://issues.apache.org/jira/browse/PHOENIX-4249 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-4219) Index gets out of sync on HBase 1.x

[ https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185148#comment-16185148 ] Vincent Poon commented on PHOENIX-4219: --- Yea I've been looking and seeing weird things as well -

[jira] [Commented] (PHOENIX-4248) Breakup IndexExpressionIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185141#comment-16185141 ] Samarth Jain commented on PHOENIX-4248: --- [~jamestaylor] - don't the tests need to end with *IT?.

[jira] [Commented] (PHOENIX-4219) Index gets out of sync on HBase 1.x

[ https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185137#comment-16185137 ] Samarth Jain commented on PHOENIX-4219: --- The test fails with single thread too. At this point, I

[jira] [Updated] (PHOENIX-4248) Breakup IndexExpressionIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4248: -- Attachment: PHOENIX-4248.patch > Breakup IndexExpressionIT into several integration tests so

[jira] [Created] (PHOENIX-4248) Breakup IndexExpressionIT into several integration tests so as not to create too many tables in one test

James Taylor created PHOENIX-4248: - Summary: Breakup IndexExpressionIT into several integration tests so as not to create too many tables in one test Key: PHOENIX-4248 URL:

[jira] [Commented] (PHOENIX-4096) Disallow DML operations on connections with CURRENT_SCN set

[ https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185111#comment-16185111 ] Thomas D'Silva commented on PHOENIX-4096: - +1 I committed my change to convert UpsertValuesIT

[jira] [Created] (PHOENIX-4247) Phoenix/Spark/ZK connection

Kumar Palaniappan created PHOENIX-4247: -- Summary: Phoenix/Spark/ZK connection Key: PHOENIX-4247 URL: https://issues.apache.org/jira/browse/PHOENIX-4247 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4187: Attachment: (was: PHOENIX-4187-v2-master.patch) > Use server timestamp for

[jira] [Updated] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4187: Attachment: PHOENIX-4187-v2-master.patch Attaching patch that fixes compilation errors on

[jira] [Resolved] (PHOENIX-4241) Upon Apache Phoenix Upgraded to 4.8 we are seeing all our writes failing for index tables.

[ https://issues.apache.org/jira/browse/PHOENIX-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-4241. - Resolution: Invalid JIRA is not the place to ask user questions. Please use the

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185000#comment-16185000 ] Thomas D'Silva commented on PHOENIX-4187: - [~jamestaylor] Yes the change means it will always

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184994#comment-16184994 ] James Taylor commented on PHOENIX-4187: --- +1 on the patch. Thanks, [~tdsilva]! > Use server

[jira] [Updated] (PHOENIX-4246) Breakup join related tests into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4246: -- Attachment: PHOENIX-4246.patch > Breakup join related tests into several integration tests so

[jira] [Updated] (PHOENIX-4246) Breakup join related tests into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4246: -- Attachment: (was: PHOENIX-4246.patch) > Breakup join related tests into several

[jira] [Commented] (PHOENIX-4096) Disallow DML operations on connections with CURRENT_SCN set

[ https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184969#comment-16184969 ] Hadoop QA commented on PHOENIX-4096: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-4246) Breakup join related tests into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4246: -- Attachment: PHOENIX-4246.patch > Breakup join related tests into several integration tests so

[jira] [Created] (PHOENIX-4246) Breakup join related tests into several integration tests so as not to create too many tables in one test

James Taylor created PHOENIX-4246: - Summary: Breakup join related tests into several integration tests so as not to create too many tables in one test Key: PHOENIX-4246 URL:

[jira] [Commented] (PHOENIX-4096) Disallow DML operations on connections with CURRENT_SCN set

[ https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184865#comment-16184865 ] Hadoop QA commented on PHOENIX-4096: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184842#comment-16184842 ] Hadoop QA commented on PHOENIX-4187: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4187: Attachment: PHOENIX-4187-v2-master.patch Attaching master patch. > Use server timestamp

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184826#comment-16184826 ] Hadoop QA commented on PHOENIX-4187: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184822#comment-16184822 ] James Taylor commented on PHOENIX-4187: --- Thanks, [~tdsilva]. So for the change below, does that

[jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184814#comment-16184814 ] Sergey Soldatov commented on PHOENIX-4187: -- [~tdsilva] Could you make it applicable to the

[jira] [Updated] (PHOENIX-4245) Breakup IndexIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4245: -- Attachment: PHOENIX-4245.patch > Breakup IndexIT into several integration tests so as not to

[jira] [Updated] (PHOENIX-4244) Breakup ArrayIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4244: -- Attachment: PHOENIX-4244.patch > Breakup ArrayIT into several integration tests so as not to

[jira] [Updated] (PHOENIX-4244) Breakup ArrayIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4244: -- Attachment: (was: PHOENIX-4244.patch) > Breakup ArrayIT into several integration tests so

[jira] [Updated] (PHOENIX-4244) Breakup ArrayIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4244: -- Summary: Breakup ArrayIT into several integration tests so as not to create too many tables

[jira] [Created] (PHOENIX-4245) Breakup IndexIT into several integration tests so as not to create too many tables in one test

James Taylor created PHOENIX-4245: - Summary: Breakup IndexIT into several integration tests so as not to create too many tables in one test Key: PHOENIX-4245 URL:

[jira] [Updated] (PHOENIX-4244) Breakup IndexIT into several integration tests so as not to create too many tables in one test

[ https://issues.apache.org/jira/browse/PHOENIX-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4244: -- Attachment: PHOENIX-4244.patch > Breakup IndexIT into several integration tests so as not to

[jira] [Updated] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4187: Attachment: PHOENIX-4187-v2.patch [~samarthjain] [~jamestaylor] I have attached a v2

[jira] [Created] (PHOENIX-4244) Breakup IndexIT into several integration tests so as not to create too many tables in one test

James Taylor created PHOENIX-4244: - Summary: Breakup IndexIT into several integration tests so as not to create too many tables in one test Key: PHOENIX-4244 URL:

[jira] [Created] (PHOENIX-4243) Using rowtimestamp column with RVC causes an exception sometimes

Thomas D'Silva created PHOENIX-4243: --- Summary: Using rowtimestamp column with RVC causes an exception sometimes Key: PHOENIX-4243 URL: https://issues.apache.org/jira/browse/PHOENIX-4243 Project:

[jira] [Updated] (PHOENIX-4096) Disallow DML operations on connections with CURRENT_SCN set

[ https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4096: -- Attachment: PHOENIX-4096_v3.patch Updated patch which removes invalid indexing tests. >

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184710#comment-16184710 ] Sergey Soldatov commented on PHOENIX-3112: -- [~jamestaylor] I would. We also discussed this

[jira] [Created] (PHOENIX-4242) Fix Indexer post-compact hook logging of NPE and TableNotFound

Vincent Poon created PHOENIX-4242: - Summary: Fix Indexer post-compact hook logging of NPE and TableNotFound Key: PHOENIX-4242 URL: https://issues.apache.org/jira/browse/PHOENIX-4242 Project: Phoenix

[jira] [Updated] (PHOENIX-4096) Disallow DML operations on connections with CURRENT_SCN set

[ https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4096: -- Attachment: PHOENIX-4096_v2.patch Please review, [~tdsilva]. I've marked both UpertValuesIT

[jira] [Created] (PHOENIX-4241) Upon Apache Phoenix Upgraded to 4.8 we are seeing all our writes failing for index tables.

Abhishek A R created PHOENIX-4241: - Summary: Upon Apache Phoenix Upgraded to 4.8 we are seeing all our writes failing for index tables. Key: PHOENIX-4241 URL: https://issues.apache.org/jira/browse/PHOENIX-4241

[jira] [Commented] (PHOENIX-4232) Hide shadow cell and commit table access in TAL

[ https://issues.apache.org/jira/browse/PHOENIX-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184538#comment-16184538 ] James Taylor commented on PHOENIX-4232: --- I think a filter would work fine for the case where the

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184487#comment-16184487 ] James Taylor commented on PHOENIX-3112: --- Good explanation, [~sergey.soldatov]. Would you mind

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184416#comment-16184416 ] Josh Elser commented on PHOENIX-3112: - {code} @Override public boolean next(List result)

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184336#comment-16184336 ] Sergey Soldatov commented on PHOENIX-3112: -- [~jamestaylor] [~an...@apache.org] [~elserj] could