[jira] [Updated] (PHOENIX-5872) Close Internal Phoenix Connections that were running during cancel
[ https://issues.apache.org/jira/browse/PHOENIX-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5872: - Attachment: PHOENIX-5872v3.4.x.patch > Close Internal Phoenix Connections that were running during cancel > -- > > Key: PHOENIX-5872 > URL: https://issues.apache.org/jira/browse/PHOENIX-5872 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3, 4.x >Reporter: Daniel Wong >Assignee: Daniel Wong >Priority: Major > Attachments: PHOENIX-5872.4.x.patch, PHOENIX-5872v2.4.x.patch, > PHOENIX-5872v3.4.x.patch > > Time Spent: 5h 20m > Remaining Estimate: 0h > > 3 part approach: > 1 don't count internal phoenix connections toward the client limit. > 2 count internal phoenix connections toward a newly defined limit > 3 track parent and child relationships between connections to close those > connections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5872) Close Internal Phoenix Connections that were running during cancel
[ https://issues.apache.org/jira/browse/PHOENIX-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5872: - Attachment: (was: PHOENIX-5872v2.4.x.patch) > Close Internal Phoenix Connections that were running during cancel > -- > > Key: PHOENIX-5872 > URL: https://issues.apache.org/jira/browse/PHOENIX-5872 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3, 4.x >Reporter: Daniel Wong >Assignee: Daniel Wong >Priority: Major > Attachments: PHOENIX-5872.4.x.patch, PHOENIX-5872v2.4.x.patch > > Time Spent: 5h 20m > Remaining Estimate: 0h > > 3 part approach: > 1 don't count internal phoenix connections toward the client limit. > 2 count internal phoenix connections toward a newly defined limit > 3 track parent and child relationships between connections to close those > connections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5872) Close Internal Phoenix Connections that were running during cancel
[ https://issues.apache.org/jira/browse/PHOENIX-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5872: - Attachment: PHOENIX-5872v2.4.x.patch > Close Internal Phoenix Connections that were running during cancel > -- > > Key: PHOENIX-5872 > URL: https://issues.apache.org/jira/browse/PHOENIX-5872 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3, 4.x >Reporter: Daniel Wong >Assignee: Daniel Wong >Priority: Major > Attachments: PHOENIX-5872.4.x.patch, PHOENIX-5872v2.4.x.patch > > Time Spent: 5h 20m > Remaining Estimate: 0h > > 3 part approach: > 1 don't count internal phoenix connections toward the client limit. > 2 count internal phoenix connections toward a newly defined limit > 3 track parent and child relationships between connections to close those > connections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5872) Close Internal Phoenix Connections that were running during cancel
[ https://issues.apache.org/jira/browse/PHOENIX-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5872: - Attachment: PHOENIX-5872v2.4.x.patch > Close Internal Phoenix Connections that were running during cancel > -- > > Key: PHOENIX-5872 > URL: https://issues.apache.org/jira/browse/PHOENIX-5872 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3, 4.x >Reporter: Daniel Wong >Assignee: Daniel Wong >Priority: Major > Attachments: PHOENIX-5872.4.x.patch, PHOENIX-5872v2.4.x.patch > > Time Spent: 5h 20m > Remaining Estimate: 0h > > 3 part approach: > 1 don't count internal phoenix connections toward the client limit. > 2 count internal phoenix connections toward a newly defined limit > 3 track parent and child relationships between connections to close those > connections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
[ https://issues.apache.org/jira/browse/PHOENIX-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5863: -- Attachment: PHOENIX-5863.4.x.v1.patch > Upsert into view against a table with index throws exception when 4.14.3 > client connects to 4.16 server > --- > > Key: PHOENIX-5863 > URL: https://issues.apache.org/jira/browse/PHOENIX-5863 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Blocker > Attachments: PHOENIX-5863.4.x.v1.patch > > > Steps to reproduce: > # Bring up a 4.16 server ( current 4.x branch) > # Connect a 4.14.3 client to the server and execute below queries > # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 > VARCHAR(10)); > # CREATE INDEX T1_IDX ON T1(V1); > # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; > # UPSERT INTO T1_V1(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below > exception*** > *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: > Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one > index write failed after retries,serverTimestamp=1587513404084,* > *at > org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* > *at > org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* > *at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* > *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* > *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* > *Caused by: > org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: > disableIndexOnFailure=false, Failed to write to multiple index tables: > [V2#I2|#I2]* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* > *... 21 more* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5877) Add indexing support in backward compat test framework
Sandeep Guggilam created PHOENIX-5877: - Summary: Add indexing support in backward compat test framework Key: PHOENIX-5877 URL: https://issues.apache.org/jira/browse/PHOENIX-5877 Project: Phoenix Issue Type: Improvement Reporter: Sandeep Guggilam We need to add the indexing support as part of backward compatibility test framework introduced as part of PHOENIX-5607 to catch any indexing related bugs when old client connects to the updated server -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
[ https://issues.apache.org/jira/browse/PHOENIX-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam reassigned PHOENIX-5863: - Assignee: Sandeep Guggilam > Upsert into view against a table with index throws exception when 4.14.3 > client connects to 4.16 server > --- > > Key: PHOENIX-5863 > URL: https://issues.apache.org/jira/browse/PHOENIX-5863 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Blocker > > Steps to reproduce: > # Bring up a 4.16 server ( current 4.x branch) > # Connect a 4.14.3 client to the server and execute below queries > # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 > VARCHAR(10)); > # CREATE INDEX T1_IDX ON T1(V1); > # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; > # UPSERT INTO T1_V1(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below > exception*** > *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: > Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one > index write failed after retries,serverTimestamp=1587513404084,* > *at > org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* > *at > org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* > *at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* > *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* > *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* > *Caused by: > org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: > disableIndexOnFailure=false, Failed to write to multiple index tables: > [V2#I2|#I2]* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* > *... 21 more* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5876) IndexTool updates the index state when it runs with ONLY option
Weiming Wang created PHOENIX-5876: - Summary: IndexTool updates the index state when it runs with ONLY option Key: PHOENIX-5876 URL: https://issues.apache.org/jira/browse/PHOENIX-5876 Project: Phoenix Issue Type: Bug Reporter: Weiming Wang Assignee: Weiming Wang When IndexTool runs with ONLY option, it is NOT supposed to update the index state, since it never rebuild the index. However current code is working the opposite way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5875) Optional logging for IndexTool verification
Kadir OZDEMIR created PHOENIX-5875: -- Summary: Optional logging for IndexTool verification Key: PHOENIX-5875 URL: https://issues.apache.org/jira/browse/PHOENIX-5875 Project: Phoenix Issue Type: Improvement Affects Versions: 4.14.3, 5.0.0 Reporter: Kadir OZDEMIR IndexTool logs information about each row that has a verification failure. The amount of logging can be excessive for large index tables. Also for some runs, we may want to just do incremental repair, i.e., repair only the rows that are broken, using -v BOTH or -v BEFORE, but not interested in the details of how they are broken. Thus, IndexTool should have an option to disable logging, something like, -dl (--disable-logging) BEFORE | AFTER | BOTH where BEFORE, AFTER and BOTH indicate at the which phase (before or after index repair or a both phases ) logging is disabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5874) IndexTool does not set TTL on its log tables correctly
Kadir OZDEMIR created PHOENIX-5874: -- Summary: IndexTool does not set TTL on its log tables correctly Key: PHOENIX-5874 URL: https://issues.apache.org/jira/browse/PHOENIX-5874 Project: Phoenix Issue Type: Bug Affects Versions: 4.14.3, 5.0.0 Reporter: Kadir OZDEMIR IndexTool does not use the correct API to set 7 day TTL on its log tables. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5858) Add commit/rollback support to the python client
[ https://issues.apache.org/jira/browse/PHOENIX-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5858. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed > Add commit/rollback support to the python client > > > Key: PHOENIX-5858 > URL: https://issues.apache.org/jira/browse/PHOENIX-5858 > Project: Phoenix > Issue Type: Sub-task > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5857) Get the python test suite working
[ https://issues.apache.org/jira/browse/PHOENIX-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5857. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed > Get the python test suite working > - > > Key: PHOENIX-5857 > URL: https://issues.apache.org/jira/browse/PHOENIX-5857 > Project: Phoenix > Issue Type: Sub-task >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > > Get the python test suite working > * add support for the new authentication options across the suite > * Find a way to run the python test suite from the Java test suite, or to > start PQS test instances from the Python test suite. Starting from > SecureQueryServerPhoenixDBIT seems to be the easiest way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5859) Add Array support to the python driver
[ https://issues.apache.org/jira/browse/PHOENIX-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5859. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed > Add Array support to the python driver > -- > > Key: PHOENIX-5859 > URL: https://issues.apache.org/jira/browse/PHOENIX-5859 > Project: Phoenix > Issue Type: Sub-task > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
