[jira] [Commented] (PHOENIX-4503) Phoenix-Spark plugin doesn't release zookeeper connections

[ https://issues.apache.org/jira/browse/PHOENIX-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337086#comment-16337086 ] Karan Mehta commented on PHOENIX-4503: -- PHOENIX-4489 has been committed today, [~sn

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337080#comment-16337080 ] Karan Mehta commented on PHOENIX-4489: -- Pushed the patches to all 4.x and 5.x branc

[jira] [Updated] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-4489: - Attachment: PHOENIX-4489.4.x-HBase-0.98.001.patch > HBase Connection leak in Phoenix MR Jobs > -

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

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

[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=16336880#comment-16336880 ] Sergey Soldatov commented on PHOENIX-4534: -- LGTM. +1 > upsert/delete/upsert fo

[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=16336808#comment-16336808 ] James Taylor commented on PHOENIX-4550: --- The QualifierEncodingScheme is just an en

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336799#comment-16336799 ] James Taylor commented on PHOENIX-4489: --- All 4.x and 5.x branches, please. > HBas

[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=16336785#comment-16336785 ] Thomas D'Silva commented on PHOENIX-4550: - We already serialize the QualifierEnc

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336784#comment-16336784 ] Karan Mehta commented on PHOENIX-4489: -- Apart from master branch, will other branch

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336783#comment-16336783 ] Karan Mehta commented on PHOENIX-4489: -- Thanks [~gjacoby] and [~jmahonin]. Will com

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336717#comment-16336717 ] Josh Mahonin commented on PHOENIX-4489: --- Thanks for that [~karanmehta93], +1 as we

[jira] [Commented] (PHOENIX-4552) Allow ROW_TIMESTAMP declaration for non PK column

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336703#comment-16336703 ] James Taylor commented on PHOENIX-4552: --- If you handle schema drift by either sett

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336670#comment-16336670 ] Geoffrey Jacoby commented on PHOENIX-4489: -- +1, [~karanmehta93] > HBase Connec

[jira] [Updated] (PHOENIX-4552) Allow ROW_TIMESTAMP declaration for non PK column

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4552: -- Summary: Allow ROW_TIMESTAMP declaration for non PK column (was: Add support for a ROW_TIMEST

[jira] [Commented] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336646#comment-16336646 ] Stephen Petschulat commented on PHOENIX-4552: - We store the column info in o

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336604#comment-16336604 ] Karan Mehta commented on PHOENIX-4489: -- [~jmahonin] Added the new patch without whi

[jira] [Updated] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-4489: - Attachment: PHOENIX-4489.002.patch > HBase Connection leak in Phoenix MR Jobs >

[jira] [Commented] (PHOENIX-4130) Avoid server retries for mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336596#comment-16336596 ] James Taylor commented on PHOENIX-4130: --- This is tricky. We'll only have our clien

[jira] [Commented] (PHOENIX-4130) Avoid server retries for mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336559#comment-16336559 ] Vincent Poon commented on PHOENIX-4130: --- [~jamestaylor] Since we are now retrying

[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=16336531#comment-16336531 ] James Taylor commented on PHOENIX-4550: --- The difficultly with the map idea is that

[jira] [Comment Edited] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336427#comment-16336427 ] James Taylor edited comment on PHOENIX-4552 at 1/23/18 9:55 PM: --

[jira] [Commented] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336427#comment-16336427 ] James Taylor commented on PHOENIX-4552: --- bq. Is it possible to have upsert set the

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

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

[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=16336280#comment-16336280 ] Thomas D'Silva commented on PHOENIX-4550: - [~jamestaylor] Another way to deal w

[jira] [Commented] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336278#comment-16336278 ] Stephen Petschulat commented on PHOENIX-4552: - Is it possible to have upsert

[jira] [Commented] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336270#comment-16336270 ] Stephen Petschulat commented on PHOENIX-4552: - > There might be a middle gro

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336213#comment-16336213 ] Rajeshbabu Chintaguntla commented on PHOENIX-4551: -- Correct [~jamestayl

[jira] [Updated] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-4551: - Attachment: PHOENIX-4551_v3.patch > Possible ColumnAlreadyExistsExceptio

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336205#comment-16336205 ] James Taylor commented on PHOENIX-4551: --- Original patch should be fine if you use

[jira] [Commented] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336193#comment-16336193 ] James Taylor commented on PHOENIX-4552: --- Nice example, [~spetschu]. It sparked my

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336190#comment-16336190 ] Rajeshbabu Chintaguntla commented on PHOENIX-4551: -- There are test fail

[jira] [Updated] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-4551: - Attachment: PHOENIX-4551_v2.patch > Possible ColumnAlreadyExistsExceptio

[jira] [Updated] (PHOENIX-590) Provide multiple versions support in external HBase tables

[ https://issues.apache.org/jira/browse/PHOENIX-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-590: - Priority: Minor (was: Blocker) > Provide multiple versions support in external HBase tables > --

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336123#comment-16336123 ] Karan Mehta commented on PHOENIX-4489: -- [~jamestaylor] I will upload a new patch wi

[jira] [Commented] (PHOENIX-4503) Phoenix-Spark plugin doesn't release zookeeper connections

[ https://issues.apache.org/jira/browse/PHOENIX-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336119#comment-16336119 ] James Taylor commented on PHOENIX-4503: --- [~snalap...@dataken.net] - would it be po

[jira] [Commented] (PHOENIX-4489) HBase Connection leak in Phoenix MR Jobs

[ https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336118#comment-16336118 ] James Taylor commented on PHOENIX-4489: --- Where are we at with this one, [~karanmeh

[jira] [Comment Edited] (PHOENIX-4502) Phoenix-Spark plugin doesn't release zookeeper connections

[ https://issues.apache.org/jira/browse/PHOENIX-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335571#comment-16335571 ] James Taylor edited comment on PHOENIX-4502 at 1/23/18 5:30 PM: --

[jira] [Created] (PHOENIX-4552) Add support for a ROW_TIMESTAMP that doesn't affect the primary key

Stephen Petschulat created PHOENIX-4552: --- Summary: Add support for a ROW_TIMESTAMP that doesn't affect the primary key Key: PHOENIX-4552 URL: https://issues.apache.org/jira/browse/PHOENIX-4552 P

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336002#comment-16336002 ] James Taylor commented on PHOENIX-4551: --- +1. Thanks, [~rajeshbabu]! > Possible Co

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335936#comment-16335936 ] Rajeshbabu Chintaguntla commented on PHOENIX-4551: -- [~jamestaylor] Sorr

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335929#comment-16335929 ] James Taylor commented on PHOENIX-4551: --- This is just for 5.x, right? Have you mer

[jira] [Updated] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-4551: - Attachment: PHOENIX-4551.patch > Possible ColumnAlreadyExistsException i

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335886#comment-16335886 ] Rajeshbabu Chintaguntla commented on PHOENIX-4551: -- This is possible ev

[jira] [Updated] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-4551: - Reporter: Romil Choksi (was: Rajeshbabu Chintaguntla) > Possible Column

[jira] [Created] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

Rajeshbabu Chintaguntla created PHOENIX-4551: Summary: Possible ColumnAlreadyExistsException is thrown from delete when autocommit off Key: PHOENIX-4551 URL: https://issues.apache.org/jira/browse/PHOEN

[jira] [Updated] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-4551: - Description: Here are the simple steps to reproduce it. {noformat} 0: j

[jira] [Closed] (PHOENIX-4502) Phoenix-Spark plugin doesn't release zookeeper connections

[ https://issues.apache.org/jira/browse/PHOENIX-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suhas Nalapure closed PHOENIX-4502. --- Duplicate of 4503. > Phoenix-Spark plugin doesn't release zookeeper connections > -

[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=16335541#comment-16335541 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- In these four I am

[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=16335537#comment-16335537 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- [~sergey.soldatov]

[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=16335508#comment-16335508 ] Sergey Soldatov commented on PHOENIX-4534: -- Not sure whether it's related or no

[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=16335478#comment-16335478 ] Sergey Soldatov commented on PHOENIX-4534: -- [~rajeshbabu] Great. Looks reasonab