[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&focusedCommentId=16167393#comment-16167393 ] Hadoop QA commented on PHOENIX-4007: {color:red}-1 overall{color}. Here are the res

[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_v4.patch v4 patch - ExplainPlanWithStatsDisabledIT was not using the

[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&focusedCommentId=16167327#comment-16167327 ] Hadoop QA commented on PHOENIX-4007: {color:red}-1 overall{color}. Here are the res

[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_v3.patch Patch that fixes the test failures. We no longer report 0 by

[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&focusedCommentId=16167256#comment-16167256 ] Hadoop QA commented on PHOENIX-4007: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167190#comment-16167190 ] Mikhail Antonov commented on PHOENIX-3111: -- Thanks for the heads up [~apurtell]

[jira] [Commented] (PHOENIX-4189) Avoid direct use of ObjectInputStream in Hive integration

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

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167136#comment-16167136 ] Vincent Poon commented on PHOENIX-3111: --- opened PHOENIX-4214 , please move the dis

[jira] [Updated] (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:all-tabpanel ] Vincent Poon updated PHOENIX-4214: -- Attachment: splitDuringUpsertSelect_wip.patch Here's a patch that has following tests to repro

[jira] [Updated] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3111: -- Attachment: (was: splitDuringUpsertSelect.patch) > Possible Deadlock/delay while building

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

Vincent Poon created PHOENIX-4214: - Summary: Scans which write should not block region split or close Key: PHOENIX-4214 URL: https://issues.apache.org/jira/browse/PHOENIX-4214 Project: Phoenix

[jira] [Comment Edited] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[ https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167133#comment-16167133 ] Mujtaba Chohan edited comment on PHOENIX-4199 at 9/15/17 12:09 AM: ---

[jira] [Updated] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[ https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-4199: Attachment: PHOENIX-4199_v2.patch Need your insight here [~jamestaylor]. Now down to last

[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_v2.patch v2 patch with an additional test for the case when one table

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167121#comment-16167121 ] Sergey Soldatov commented on PHOENIX-3111: -- +1 for the new JiRA. I also like [~

[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&focusedCommentId=16167119#comment-16167119 ] Hadoop QA commented on PHOENIX-4007: {color:red}-1 overall{color}. Here are the res

[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_v1.patch [~jamestaylor], please review. > Surface time at which byte

[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: -- Summary: Surface time at which byte/row estimate information was computed in explain plan outp

[jira] [Updated] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[ https://issues.apache.org/jira/browse/PHOENIX-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-4204: Attachment: PHOENIX-4204_v2.patch [~jamestaylor] PHOENIX-4204_v2.patch will all passing te

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167072#comment-16167072 ] Josh Elser commented on PHOENIX-3111: - Should we move conversation over to a new JIR

[jira] [Updated] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3111: -- Attachment: splitDuringUpsertSelect.patch Here's a patch that has following tests to reproduce

[jira] [Commented] (PHOENIX-4207) Improve zombie detection in test-patch.sh

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

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

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

[jira] [Updated] (PHOENIX-4213) Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN

[ https://issues.apache.org/jira/browse/PHOENIX-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-4213: Attachment: PHOENIX-4213.patch > Modify ExtendedQueryExecIT and FunkyNamesIT to not use cu

[jira] [Created] (PHOENIX-4213) Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN

Mujtaba Chohan created PHOENIX-4213: --- Summary: Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN Key: PHOENIX-4213 URL: https://issues.apache.org/jira/browse/PHOENIX-4213 Project: Ph

[jira] [Created] (PHOENIX-4212) Disallow DML operations on connections with CURRENT_SCN set - DerivedTableIT

Ethan Wang created PHOENIX-4212: --- Summary: Disallow DML operations on connections with CURRENT_SCN set - DerivedTableIT Key: PHOENIX-4212 URL: https://issues.apache.org/jira/browse/PHOENIX-4212 Project:

[jira] [Commented] (PHOENIX-4210) Upgrade to Tephra 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166864#comment-16166864 ] Hadoop QA commented on PHOENIX-4210: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166831#comment-16166831 ] Josh Elser commented on PHOENIX-3111: - bq. My comment on it (ignored) was "This is c

java.lang.IllegalAccessError: com/google/protobuf/HBaseZeroCopyByteString

Hi All, I am facing this issue while trying to insert from spark to Pheonix. Tried adding /protobuf-java-2.5.0.jar, hbase-protocol-0.98.9-hadoop2.jar and all other dependencies to the path but still unable to resolve the error. How to resolve the issue. Please find the complete error log below

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166789#comment-16166789 ] stack commented on PHOENIX-3111: Funny. I took a look at HBASE-14893. My comment on it (

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166659#comment-16166659 ] Rahul Shrivastava commented on PHOENIX-3655: Thanks [~elserj] I will start

[jira] [Commented] (PHOENIX-4211) Change tephra dependency in phoenix-kafka to test dependency like other poms

[ https://issues.apache.org/jira/browse/PHOENIX-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166605#comment-16166605 ] Josh Elser commented on PHOENIX-4211: - +1 yup, looks like it to me. {{mvn dependency

[jira] [Comment Edited] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166604#comment-16166604 ] Andrew Purtell edited comment on PHOENIX-3111 at 9/14/17 5:06 PM:

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166604#comment-16166604 ] Andrew Purtell commented on PHOENIX-3111: - bq. From HBase side we need to revert

[jira] [Updated] (PHOENIX-4211) Change tephra dependency in phoenix-kafka to test dependency like other poms

[ https://issues.apache.org/jira/browse/PHOENIX-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4211: -- Attachment: PHOENIX-4211.patch [~elserj] - does this change make sense? I noticed the inconsis

[jira] [Assigned] (PHOENIX-4211) Change tephra dependency in phoenix-kafka to test dependency like other poms

[ https://issues.apache.org/jira/browse/PHOENIX-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4211: - Assignee: James Taylor > Change tephra dependency in phoenix-kafka to test dependency l

[jira] [Created] (PHOENIX-4211) Change tephra dependency in phoenix-kafka to test dependency like other poms

James Taylor created PHOENIX-4211: - Summary: Change tephra dependency in phoenix-kafka to test dependency like other poms Key: PHOENIX-4211 URL: https://issues.apache.org/jira/browse/PHOENIX-4211 Proj

[jira] [Updated] (PHOENIX-4210) Upgrade to Tephra 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4210: -- Attachment: PHOENIX-4210.patch > Upgrade to Tephra 0.13 > -- > >

[jira] [Created] (PHOENIX-4210) Upgrade to Tephra 0.13

James Taylor created PHOENIX-4210: - Summary: Upgrade to Tephra 0.13 Key: PHOENIX-4210 URL: https://issues.apache.org/jira/browse/PHOENIX-4210 Project: Phoenix Issue Type: Bug Repo

[jira] [Assigned] (PHOENIX-4210) Upgrade to Tephra 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4210: - Assignee: James Taylor > Upgrade to Tephra 0.13 > -- > >

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

[ https://issues.apache.org/jira/browse/PHOENIX-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166449#comment-16166449 ] James Taylor commented on PHOENIX-4209: --- +1. Thanks, [~aertoria]. I'll get this co

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

[ https://issues.apache.org/jira/browse/PHOENIX-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166163#comment-16166163 ] Hadoop QA commented on PHOENIX-4209: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165961#comment-16165961 ] Samarth Jain commented on PHOENIX-3111: --- By failing the query I meant throwing a r

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165942#comment-16165942 ] Rajeshbabu Chintaguntla commented on PHOENIX-3111: -- bq. On failing the

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165915#comment-16165915 ] Samarth Jain commented on PHOENIX-3111: --- On failing the query, in the finally bloc

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

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

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165910#comment-16165910 ] Rajeshbabu Chintaguntla commented on PHOENIX-3111: -- bq. Would a better

[jira] [Comment Edited] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165869#comment-16165869 ] Rajeshbabu Chintaguntla edited comment on PHOENIX-3111 at 9/14/17 7:29 AM: ---

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165879#comment-16165879 ] Samarth Jain commented on PHOENIX-3111: --- Would a better alternative be to not do t

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

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

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165854#comment-16165854 ] James Taylor commented on PHOENIX-3111: --- [~sergey.soldatov], [~enis] - we're seein