[jira] [Commented] (PHOENIX-4547) Use hbase 2.0.0-beta-1

[ https://issues.apache.org/jira/browse/PHOENIX-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334572#comment-16334572 ] Josh Elser commented on PHOENIX-4547: - Thanks, Rajesh! > Use hbase 2.0.0-beta-1 > -

[jira] [Commented] (PHOENIX-3534) Support multi region SYSTEM.CATALOG table

[ https://issues.apache.org/jira/browse/PHOENIX-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334603#comment-16334603 ] James Taylor commented on PHOENIX-3534: --- FYI, the patch is now on the system-catal

[jira] [Created] (PHOENIX-4548) UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant views that have the same name.

Thomas D'Silva created PHOENIX-4548: --- Summary: UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant views that have the same name. Key: PHOENIX-4548 URL: https://issues.apache.org/jira/browse/PHOENI

[jira] [Updated] (PHOENIX-4548) UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant views that have the same name.

[ https://issues.apache.org/jira/browse/PHOENIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4548: Attachment: PHOENIX-4548.patch > UpgradeUtil.mapChildViewsToNamespace does not handle mult

RE: [ANNOUNCE] Apache Phoenix 4.13.2 for CDH 5.11.2 released

Is there any documentation on cloudera site where it is announced about this news. I checked with cloudera team and they are still not aware of this. Regards, CM +1 201 763 1656 -Original Message- From: James Taylor [mailto:jamestay...@apache.org] Sent: Saturday, January 20, 2018 6:02

[jira] [Commented] (PHOENIX-4531) Delete on a table with a global mutable index can issue client-side deletes against the index

[ https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334817#comment-16334817 ] Vincent Poon commented on PHOENIX-4531: --- [~jamestaylor] could you create a version

Re: [DISCUSS] 5.0.0-beta release before month's end?

Have you guys back ported the removal of deprecated APIs patches to the 4.x branches? That'll probably help minimize the merge conflicts we see going forward. On Thu, Jan 18, 2018 at 1:03 PM, James Taylor wrote: > Awesome! That's great work!! > > On Thu, Jan 18, 2018 at 1:00 PM, Josh Elser wrot

[jira] [Updated] (PHOENIX-4531) Delete on a table with a global mutable index can issue client-side deletes against the index

[ https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4531: -- Fix Version/s: 4.14.0 > Delete on a table with a global mutable index can issue client-side de

[jira] [Commented] (PHOENIX-4531) Delete on a table with a global mutable index can issue client-side deletes against the index

[ https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334853#comment-16334853 ] James Taylor commented on PHOENIX-4531: --- Thanks, [~vincentpoon]. Looks like 4.x-HB

[jira] [Commented] (PHOENIX-4531) Delete on a table with a global mutable index can issue client-side deletes against the index

[ https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334858#comment-16334858 ] Josh Elser commented on PHOENIX-4531: - cc/ [~sergey.soldatov] [~rajeshbabu] > Delet

[jira] [Commented] (PHOENIX-4531) Delete on a table with a global mutable index can issue client-side deletes against the index

[ https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334861#comment-16334861 ] Josh Elser commented on PHOENIX-4531: - Also, I have it on my list to go back through

[jira] [Commented] (PHOENIX-4531) Delete on a table with a global mutable index can issue client-side deletes against the index

[ https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334878#comment-16334878 ] Hudson commented on PHOENIX-4531: - FAILURE: Integrated in Jenkins build Phoenix-master #

[jira] [Updated] (PHOENIX-4382) Immutable table SINGLE_CELL_ARRAY_WITH_OFFSETS values starting with separator byte return null in query results

[ https://issues.apache.org/jira/browse/PHOENIX-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4382: -- Fix Version/s: 4.13.2 > Immutable table SINGLE_CELL_ARRAY_WITH_OFFSETS values starting with se

[jira] [Updated] (PHOENIX-4382) Immutable table SINGLE_CELL_ARRAY_WITH_OFFSETS values starting with separator byte return null in query results

[ https://issues.apache.org/jira/browse/PHOENIX-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4382: -- Fix Version/s: 4.13.2-cdh5.11.2 > Immutable table SINGLE_CELL_ARRAY_WITH_OFFSETS values starti

[jira] [Updated] (PHOENIX-4549) Pherf - Column override and sequenced index creation support

[ https://issues.apache.org/jira/browse/PHOENIX-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-4549: Attachment: PHOENIX-4549.patch > Pherf - Column override and sequenced index creation supp

[jira] [Created] (PHOENIX-4549) Pherf - Column override and sequenced index creation support

Mujtaba Chohan created PHOENIX-4549: --- Summary: Pherf - Column override and sequenced index creation support Key: PHOENIX-4549 URL: https://issues.apache.org/jira/browse/PHOENIX-4549 Project: Phoenix

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335094#comment-16335094 ] Josh Elser commented on PHOENIX-4537: - I've been unsuccessful in making an IT for th

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335132#comment-16335132 ] Sergey Soldatov commented on PHOENIX-4537: -- [~elserj] honestly speaking I'm not

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335134#comment-16335134 ] Josh Elser commented on PHOENIX-4537: - bq. honestly speaking I'm not very happy that

[jira] [Commented] (PHOENIX-4546) Projected immutable table cannot be read through ProjectedColumnExpression

[ https://issues.apache.org/jira/browse/PHOENIX-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335167#comment-16335167 ] Sergey Soldatov commented on PHOENIX-4546: -- I'm not sure whether it's a valid c

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335178#comment-16335178 ] James Taylor commented on PHOENIX-4537: --- The upgrade *should not* happen from a se

[jira] [Comment Edited] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335178#comment-16335178 ] James Taylor edited comment on PHOENIX-4537 at 1/22/18 11:47 PM: -

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335181#comment-16335181 ] Josh Elser commented on PHOENIX-4537: - bq. The upgrade should not happen from a serv

[jira] [Comment Edited] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335181#comment-16335181 ] Josh Elser edited comment on PHOENIX-4537 at 1/22/18 11:55 PM: ---

[jira] [Commented] (PHOENIX-4548) UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant views that have the same name.

[ https://issues.apache.org/jira/browse/PHOENIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335192#comment-16335192 ] Thomas D'Silva commented on PHOENIX-4548: - [~an...@apache.org] can you please ta

[jira] [Assigned] (PHOENIX-4529) Users should only require RX access to SYSTEM.SEQUENCE table

[ https://issues.apache.org/jira/browse/PHOENIX-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva reassigned PHOENIX-4529: --- Assignee: Thomas D'Silva > Users should only require RX access to SYSTEM.SEQUENCE t

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335197#comment-16335197 ] Sergey Soldatov commented on PHOENIX-4537: -- I doubt that PHOENIX-4530 would mak

[jira] [Commented] (PHOENIX-4529) Users should only require RX access to SYSTEM.SEQUENCE table

[ https://issues.apache.org/jira/browse/PHOENIX-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335206#comment-16335206 ] Andrew Purtell commented on PHOENIX-4529: - Cell level ACLs have limitations you

Re: [DISCUSS] 5.0.0-beta release before month's end?

I don't think so. We (I use that loosely -- I'd hardly lump my contributions to this effort in the same room as the contributions of the others) have been moving fast to get back to functional state. This have definitely lapsed. It is a blocker to make sure 5.x isn't missing stuff from 4.x and

[jira] [Comment Edited] (PHOENIX-4529) Users should only require RX access to SYSTEM.SEQUENCE table

[ https://issues.apache.org/jira/browse/PHOENIX-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335206#comment-16335206 ] Andrew Purtell edited comment on PHOENIX-4529 at 1/23/18 12:33 AM: ---

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335228#comment-16335228 ] James Taylor commented on PHOENIX-4537: --- [~sergey.soldatov] - good point. PHOENIX-

[jira] [Commented] (PHOENIX-4537) RegionServer initiating compaction can trigger schema migration and deadlock the system

[ https://issues.apache.org/jira/browse/PHOENIX-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335235#comment-16335235 ] Josh Elser commented on PHOENIX-4537: - bq. I'm hoping it could use the same general

[jira] [Commented] (PHOENIX-4529) Users should only require RX access to SYSTEM.SEQUENCE table

[ https://issues.apache.org/jira/browse/PHOENIX-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335309#comment-16335309 ] Thomas D'Silva commented on PHOENIX-4529: - Thats good to know, thanks [~apurtell

[jira] [Created] (PHOENIX-4550) Allow declaration of max columns on base physical table

James Taylor created PHOENIX-4550: - Summary: Allow declaration of max columns on base physical table Key: PHOENIX-4550 URL: https://issues.apache.org/jira/browse/PHOENIX-4550 Project: Phoenix

[jira] [Updated] (PHOENIX-4550) Allow declaration of max columns on base physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4550: -- Issue Type: Improvement (was: Bug) > Allow declaration of max columns on base physical table

[jira] [Commented] (PHOENIX-4550) Allow declaration of max columns on base physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335340#comment-16335340 ] James Taylor commented on PHOENIX-4550: --- FYI, [~shehzaadn]. > Allow declaration o

[jira] [Commented] (PHOENIX-4550) Allow declaration of max columns on base physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335378#comment-16335378 ] Thomas D'Silva commented on PHOENIX-4550: - [~jamestaylor]  This will mainly hel

[jira] [Commented] (PHOENIX-4550) Allow declaration of max columns on base physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335385#comment-16335385 ] James Taylor commented on PHOENIX-4550: --- bq. This will mainly help for the case wh

[jira] [Updated] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-4534: - Attachment: PHOENIX-4534_v3.patch > upsert/delete/upsert for the same ro

[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335462#comment-16335462 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- [~sergey.soldatov]