[jira] [Updated] (PHOENIX-4007) Surface time at which byte/row estimate information was computed in explain plan output

[ https://issues.apache.org/jira/browse/PHOENIX-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-4007: -- Attachment: (was: PHOENIX-4007_v8.patch) > Surface time at which byte/row estimate

[jira] [Updated] (PHOENIX-4007) Surface time at which byte/row estimate information was computed in explain plan output

[ https://issues.apache.org/jira/browse/PHOENIX-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-4007: -- Attachment: PHOENIX-4007_v8.patch > Surface time at which byte/row estimate information was

[jira] [Commented] (PHOENIX-4007) Surface time at which byte/row estimate information was computed in explain plan output

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

[jira] [Updated] (PHOENIX-4007) Surface time at which byte/row estimate information was computed in explain plan output

[ https://issues.apache.org/jira/browse/PHOENIX-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-4007: -- Attachment: PHOENIX-4007_v8.patch Patch that fixes the test failures. It also fixes an issue

[jira] [Commented] (PHOENIX-4214) Scans which write should not block region split or close

[ https://issues.apache.org/jira/browse/PHOENIX-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174254#comment-16174254 ] James Taylor commented on PHOENIX-4214: --- Just want to confirm, [~lhofhansl], that your comment

[jira] [Comment Edited] (PHOENIX-4221) Disallow DML operations on connections with CURRENT_SCN set - VariableLengthPKIT

[ https://issues.apache.org/jira/browse/PHOENIX-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174231#comment-16174231 ] Ethan Wang edited comment on PHOENIX-4221 at 9/21/17 4:04 AM: --

[jira] [Comment Edited] (PHOENIX-4221) Disallow DML operations on connections with CURRENT_SCN set - VariableLengthPKIT

[ https://issues.apache.org/jira/browse/PHOENIX-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174231#comment-16174231 ] Ethan Wang edited comment on PHOENIX-4221 at 9/21/17 4:04 AM: --

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

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

[jira] [Commented] (PHOENIX-4138) Create a hard limit on number of indexes per table

[ https://issues.apache.org/jira/browse/PHOENIX-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174005#comment-16174005 ] James Taylor commented on PHOENIX-4138: --- Looks like the license header is in an unconventional

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

[ https://issues.apache.org/jira/browse/PHOENIX-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang updated PHOENIX-4221: Attachment: PHOENIX-4221.patch > Disallow DML operations on connections with CURRENT_SCN set - >

[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=16173794#comment-16173794 ] Samarth Jain commented on PHOENIX-4187: --- Most of the tests that were testing the ROW_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=16173775#comment-16173775 ] James Taylor commented on PHOENIX-4187: --- I'm surprised no tests failed, [~samarthjain]. > Use

[jira] [Updated] (PHOENIX-4183) Disallow UPSERT that specifies ROW_TIMESTAMP column value for table with mutable index

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4183: -- Description: When a table has row_timestamp column, user provided value for the column ends

[jira] [Updated] (PHOENIX-4183) Disallow UPSERT that specifies ROW_TIMESTAMP column value for table with mutable index

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4183: -- Summary: Disallow UPSERT that specifies ROW_TIMESTAMP column value for table with mutable

[jira] [Commented] (PHOENIX-4183) Disallow creating mutable indexes on tables with ROW_TIMESTAMP column

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173713#comment-16173713 ] James Taylor commented on PHOENIX-4183: --- We'd like to give an error on an UPSERT that specifies

[jira] [Comment Edited] (PHOENIX-4183) Disallow creating mutable indexes on tables with ROW_TIMESTAMP column

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173713#comment-16173713 ] James Taylor edited comment on PHOENIX-4183 at 9/20/17 7:23 PM: We'd

[jira] [Commented] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

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

[jira] [Commented] (PHOENIX-4183) Disallow creating mutable indexes on tables with ROW_TIMESTAMP column

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173661#comment-16173661 ] Thomas D'Silva commented on PHOENIX-4183: - [~samarthjain] [~jamestaylor] Should we allow using

[jira] [Commented] (PHOENIX-4183) Disallow creating mutable indexes on tables with ROW_TIMESTAMP column

[ https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173662#comment-16173662 ] Thomas D'Silva commented on PHOENIX-4183: - [~samarthjain] [~jamestaylor] Should we allow using

[jira] [Reopened] (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 ] Samarth Jain reopened PHOENIX-4187: --- Actually, I was wrong. This is still an issue. Even though HBase changes the timestamp of the

[jira] [Commented] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

[ https://issues.apache.org/jira/browse/PHOENIX-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173553#comment-16173553 ] Samarth Jain commented on PHOENIX-4220: --- +1 > Upper bound not being used in partial index

[jira] [Commented] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

[ https://issues.apache.org/jira/browse/PHOENIX-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173548#comment-16173548 ] James Taylor commented on PHOENIX-4220: --- The test will go in as part of PHOENIX-4215. It requires

[jira] [Commented] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

[ https://issues.apache.org/jira/browse/PHOENIX-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173540#comment-16173540 ] Vincent Poon commented on PHOENIX-4220: --- Is there a test we can write for this? We didn't have one

[jira] [Updated] (PHOENIX-4215) Partial index rebuild never complete after PHOENIX-3525 when rebuild period is configured

[ https://issues.apache.org/jira/browse/PHOENIX-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4215: -- Attachment: PHOENIX-4215_wip2.patch > Partial index rebuild never complete after PHOENIX-3525

[jira] [Commented] (PHOENIX-4178) Detect failed index write while rebuilder is running with index staying active

[ https://issues.apache.org/jira/browse/PHOENIX-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173473#comment-16173473 ] James Taylor commented on PHOENIX-4178: --- bq. does this only apply to mutable indexes? Yes,

[jira] [Updated] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

[ https://issues.apache.org/jira/browse/PHOENIX-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4220: -- Attachment: PHOENIX-4220.patch Please review, [~samarthjain]. I have a test with my fix for

[jira] [Updated] (PHOENIX-4215) Partial index rebuild never complete after PHOENIX-3525 when rebuild period is configured

[ https://issues.apache.org/jira/browse/PHOENIX-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4215: -- Attachment: PHOENIX-4215_wip.patch WIP patch. FYI, I will factor out the fix for PHOENIX-4220

[jira] [Created] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

James Taylor created PHOENIX-4220: - Summary: Upper bound not being used in partial index rebuilder Key: PHOENIX-4220 URL: https://issues.apache.org/jira/browse/PHOENIX-4220 Project: Phoenix

[jira] [Commented] (PHOENIX-3708) Tests introduced in PHOENIX-3346 doesn't work well with failsafe plugin

[ https://issues.apache.org/jira/browse/PHOENIX-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172864#comment-16172864 ] Csaba Skrabak commented on PHOENIX-3708: Hi [~sergey.soldatov], did the reenabled tests succeed