[jira] [Updated] (PHOENIX-6511) Deletes fail in case of failed region split
[ https://issues.apache.org/jira/browse/PHOENIX-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-6511: Fix Version/s: (was: 5.2.0) > Deletes fail in case of failed region split > --- > > Key: PHOENIX-6511 > URL: https://issues.apache.org/jira/browse/PHOENIX-6511 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.1 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 4.17.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6511) Deletes fail in case of failed region split
Abhishek Singh Chouhan created PHOENIX-6511: --- Summary: Deletes fail in case of failed region split Key: PHOENIX-6511 URL: https://issues.apache.org/jira/browse/PHOENIX-6511 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.1 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 4.17.0, 5.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6336) Scan filter is incorrectly set to null for index rebuilds
Abhishek Singh Chouhan created PHOENIX-6336: --- Summary: Scan filter is incorrectly set to null for index rebuilds Key: PHOENIX-6336 URL: https://issues.apache.org/jira/browse/PHOENIX-6336 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6048) Strict batching in index rebuilds
Abhishek Singh Chouhan created PHOENIX-6048: --- Summary: Strict batching in index rebuilds Key: PHOENIX-6048 URL: https://issues.apache.org/jira/browse/PHOENIX-6048 Project: Phoenix Issue Type: Improvement Affects Versions: 4.16.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan During rebuilds we have batching limit checks between mutations of different index keys. For the cases where a single index key might end up having many mutations, we might end up sending batches that are many times larger than our expected batch size. We should also have batching checks between the mutations for a single indexKey. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6001) Incremental rebuild/verification can result in missing rows and false positives
[ https://issues.apache.org/jira/browse/PHOENIX-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-6001: Attachment: PHOENIX-6001-master.patch > Incremental rebuild/verification can result in missing rows and false > positives > > > Key: PHOENIX-6001 > URL: https://issues.apache.org/jira/browse/PHOENIX-6001 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6001-4.x.patch, PHOENIX-6001-master.patch > > Time Spent: 10m > Remaining Estimate: 0h > > In case of incremental rebuild/verify we prepare a skip scan using page size > constraints first and then use it for rebuild, however when using this skip > scan we constraint the number of indexmutations we're going to build/verify > also on the page size. In the case where we have multiple index mutations for > single dataTableRow, we can return back to the client without scanning all > the rows of the skip scan filter, when the client does next, we resume > incorrectly from the row after the last of the previous skip scan when infact > we hadn't exhausted it fully. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6001) Incremental rebuild/verification can result in missing rows and false positives
[ https://issues.apache.org/jira/browse/PHOENIX-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-6001: Attachment: PHOENIX-6001-4.x.patch > Incremental rebuild/verification can result in missing rows and false > positives > > > Key: PHOENIX-6001 > URL: https://issues.apache.org/jira/browse/PHOENIX-6001 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6001-4.x.patch > > > In case of incremental rebuild/verify we prepare a skip scan using page size > constraints first and then use it for rebuild, however when using this skip > scan we constraint the number of indexmutations we're going to build/verify > also on the page size. In the case where we have multiple index mutations for > single dataTableRow, we can return back to the client without scanning all > the rows of the skip scan filter, when the client does next, we resume > incorrectly from the row after the last of the previous skip scan when infact > we hadn't exhausted it fully. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6001) Incremental rebuild/verification can result in missing rows and false positives
Abhishek Singh Chouhan created PHOENIX-6001: --- Summary: Incremental rebuild/verification can result in missing rows and false positives Key: PHOENIX-6001 URL: https://issues.apache.org/jira/browse/PHOENIX-6001 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 5.1.0, 4.16.0 In case of incremental rebuild/verify we prepare a skip scan using page size constraints first and then use it for rebuild, however when using this skip scan we constraint the number of indexmutations we're going to build/verify also on the page size. In the case where we have multiple index mutations for single dataTableRow, we can return back to the client without scanning all the rows of the skip scan filter, when the client does next, we resume incorrectly from the row after the last of the previous skip scan when infact we hadn't exhausted it fully. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5995) Index Rebuild page size is not honored in case of point deletes
[ https://issues.apache.org/jira/browse/PHOENIX-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5995: Affects Version/s: 4.15.0 > Index Rebuild page size is not honored in case of point deletes > --- > > Key: PHOENIX-5995 > URL: https://issues.apache.org/jira/browse/PHOENIX-5995 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5995-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5995) Index Rebuild page size is not honored in case of point deletes
[ https://issues.apache.org/jira/browse/PHOENIX-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5995: Attachment: PHOENIX-5995-4.x.patch > Index Rebuild page size is not honored in case of point deletes > --- > > Key: PHOENIX-5995 > URL: https://issues.apache.org/jira/browse/PHOENIX-5995 > Project: Phoenix > Issue Type: Bug >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5995-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5995) Index Rebuild page size is not honored in case of point deletes
Abhishek Singh Chouhan created PHOENIX-5995: --- Summary: Index Rebuild page size is not honored in case of point deletes Key: PHOENIX-5995 URL: https://issues.apache.org/jira/browse/PHOENIX-5995 Project: Phoenix Issue Type: Bug Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 5.1.0, 4.16.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5975: Attachment: PHOENIX-5975-master.patch > Index rebuild/verification page size should be configurable from IndexTool > -- > > Key: PHOENIX-5975 > URL: https://issues.apache.org/jira/browse/PHOENIX-5975 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5975-4.x.001.patch, PHOENIX-5975-4.x.002.patch, > PHOENIX-5975-4.x.patch, PHOENIX-5975-master.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5975: Attachment: PHOENIX-5975-4.x.002.patch > Index rebuild/verification page size should be configurable from IndexTool > -- > > Key: PHOENIX-5975 > URL: https://issues.apache.org/jira/browse/PHOENIX-5975 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5975-4.x.001.patch, PHOENIX-5975-4.x.002.patch, > PHOENIX-5975-4.x.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5975: Attachment: (was: PHOENIX-5975-4.x.001.patch) > Index rebuild/verification page size should be configurable from IndexTool > -- > > Key: PHOENIX-5975 > URL: https://issues.apache.org/jira/browse/PHOENIX-5975 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5975-4.x.001.patch, PHOENIX-5975-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5975: Attachment: PHOENIX-5975-4.x.001.patch > Index rebuild/verification page size should be configurable from IndexTool > -- > > Key: PHOENIX-5975 > URL: https://issues.apache.org/jira/browse/PHOENIX-5975 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5975-4.x.001.patch, PHOENIX-5975-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5975: Attachment: PHOENIX-5975-4.x.001.patch > Index rebuild/verification page size should be configurable from IndexTool > -- > > Key: PHOENIX-5975 > URL: https://issues.apache.org/jira/browse/PHOENIX-5975 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5975-4.x.001.patch, PHOENIX-5975-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5975: Attachment: PHOENIX-5975-4.x.patch > Index rebuild/verification page size should be configurable from IndexTool > -- > > Key: PHOENIX-5975 > URL: https://issues.apache.org/jira/browse/PHOENIX-5975 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5975-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5975) Index rebuild/verification page size should be configurable from IndexTool
Abhishek Singh Chouhan created PHOENIX-5975: --- Summary: Index rebuild/verification page size should be configurable from IndexTool Key: PHOENIX-5975 URL: https://issues.apache.org/jira/browse/PHOENIX-5975 Project: Phoenix Issue Type: Improvement Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 5.1.0, 4.16.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Fix Version/s: 5.1.0 > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5932-4.x.001.patch, PHOENIX-5932-4.x.001.patch, > PHOENIX-5932-4.x.patch, PHOENIX-5932-master.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > Time Spent: 2.5h > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-4.x.001.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.001.patch, PHOENIX-5932-4.x.001.patch, > PHOENIX-5932-4.x.patch, PHOENIX-5932-master.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-master.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.001.patch, PHOENIX-5932-4.x.patch, > PHOENIX-5932-master.patch, PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.patch, PHOENIX-5932-wip-master.001.patch, > PHOENIX-5932-wip-master.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-4.x.001.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.001.patch, PHOENIX-5932-4.x.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: (was: PHOENIX-5932-wip-4.x.001.patch) > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.patch, PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.patch, PHOENIX-5932-wip-master.001.patch, > PHOENIX-5932-wip-master.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: (was: PHOENIX-5932-4.x.patch) > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.patch, PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-4.x.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.patch, PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-4.x.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-4.x.patch, PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-wip-4.x.001.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: (was: PHOENIX-5932-wip-4.x.patch) > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.001.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-wip-4.x.001.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.001.patch, > PHOENIX-5932-wip-4.x.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-wip-master.001.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.001.patch, PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-wip-4.x.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.patch, PHOENIX-5932-wip-4.x.patch, > PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5931) PhoenixIndexFailurePolicy throws NPE if cause of IOE is null
[ https://issues.apache.org/jira/browse/PHOENIX-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5931: Attachment: PHOENIX-5931-master.patch > PhoenixIndexFailurePolicy throws NPE if cause of IOE is null > > > Key: PHOENIX-5931 > URL: https://issues.apache.org/jira/browse/PHOENIX-5931 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5931-4.x.001.patch, PHOENIX-5931-4.x.patch, > PHOENIX-5931-master.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5931) PhoenixIndexFailurePolicy throws NPE if cause of IOE is null
[ https://issues.apache.org/jira/browse/PHOENIX-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5931: Attachment: PHOENIX-5931-4.x.001.patch > PhoenixIndexFailurePolicy throws NPE if cause of IOE is null > > > Key: PHOENIX-5931 > URL: https://issues.apache.org/jira/browse/PHOENIX-5931 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5931-4.x.001.patch, PHOENIX-5931-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-wip-master.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.patch, PHOENIX-5932-wip-master.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Issue Type: Bug (was: Improvement) > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5932-wip-4.x.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Attachment: PHOENIX-5932-wip-4.x.patch > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Attachments: PHOENIX-5932-wip-4.x.patch > > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5932: Description: Steps to reproduce # Create a table with PK as COL1, COL2 # Create 2 views with different view constants on COL2. Also add other columns # Upsert rows into the views # Create indexes on the views. Rebuild will result in each view index having rows from other view also This is because we set the filter on scan to null during rebuild [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] was: Steps to reproduce # Create a table with PK as COL1, COL2 # Create 2 views with different view constants on COL2. Also add other columns # Upsert rows into the views # Create indexes on the views. Rebuild will result in each view index having rows from other view also This is because we set the filter on scan to null during rebuild [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084] > View Index rebuild results in surplus rows from other view indexes > -- > > Key: PHOENIX-5932 > URL: https://issues.apache.org/jira/browse/PHOENIX-5932 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > > Steps to reproduce > # Create a table with PK as COL1, COL2 > # Create 2 views with different view constants on COL2. Also add other > columns > # Upsert rows into the views > # Create indexes on the views. Rebuild will result in each view index having > rows from other view also > This is because we set the filter on scan to null during rebuild > [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5932) View Index rebuild results in surplus rows from other view indexes
Abhishek Singh Chouhan created PHOENIX-5932: --- Summary: View Index rebuild results in surplus rows from other view indexes Key: PHOENIX-5932 URL: https://issues.apache.org/jira/browse/PHOENIX-5932 Project: Phoenix Issue Type: Improvement Affects Versions: 4.16.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Steps to reproduce # Create a table with PK as COL1, COL2 # Create 2 views with different view constants on COL2. Also add other columns # Upsert rows into the views # Create indexes on the views. Rebuild will result in each view index having rows from other view also This is because we set the filter on scan to null during rebuild [here|[https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java#L1084] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5931) PhoenixIndexFailurePolicy throws NPE if cause of IOE is null
[ https://issues.apache.org/jira/browse/PHOENIX-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5931: Attachment: PHOENIX-5931-4.x.patch > PhoenixIndexFailurePolicy throws NPE if cause of IOE is null > > > Key: PHOENIX-5931 > URL: https://issues.apache.org/jira/browse/PHOENIX-5931 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5931-4.x.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5931) PhoenixIndexFailurePolicy throws NPE if cause of IOE is null
Abhishek Singh Chouhan created PHOENIX-5931: --- Summary: PhoenixIndexFailurePolicy throws NPE if cause of IOE is null Key: PHOENIX-5931 URL: https://issues.apache.org/jira/browse/PHOENIX-5931 Project: Phoenix Issue Type: Improvement Affects Versions: 4.16.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 5.1.0, 4.16.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Fix Version/s: 5.1.0 > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.001.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.master.patch > > Time Spent: 40m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.4.x.001.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.001.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.master.patch > > Time Spent: 20m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- 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 ] Abhishek Singh Chouhan updated PHOENIX-5863: Fix Version/s: 4.16.0 > 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 > Fix For: 4.16.0 > > 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] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.master.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, PHOENIX-5899.master.patch > > Time Spent: 10m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.4.x.001.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch > > Time Spent: 10m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.4.x.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.4.x.patch > > Time Spent: 10m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.4.x.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch > > Time Spent: 10m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.4.x.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.patch > > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
Abhishek Singh Chouhan created PHOENIX-5899: --- Summary: Index writes and verifications should contain information of underlying cause of failure Key: PHOENIX-5899 URL: https://issues.apache.org/jira/browse/PHOENIX-5899 Project: Phoenix Issue Type: Improvement Affects Versions: 4.15.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 4.16.0 In case of any failures during index writes, rebuild and verify we simply return MultiIndexWriteFailureException without the underlying cause. This makes finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index
[
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Singh Chouhan updated PHOENIX-5580:
Fix Version/s: (was: 4.15.1)
4.16.0
> Wrong values seen when updating a view for a table that has an index
>
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
> Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5580.4.x.v1.patch, PHOENIX-5580.4.x.v2.patch,
> PHOENIX-5580.4.x.v3.patch, PHOENIX-5580.master.v1.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
> CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
> UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5867) Add support for property overrides in IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5867: Attachment: PHOENIX-5867-master.patch > Add support for property overrides in IndexTool > --- > > Key: PHOENIX-5867 > URL: https://issues.apache.org/jira/browse/PHOENIX-5867 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5867-4.x.001.patch, PHOENIX-5867-4.x.patch, > PHOENIX-5867-master.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Add support to accept property overrides in the form of -Dproperty=value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5867) Add support for property overrides in IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5867: Attachment: PHOENIX-5867-4.x.001.patch > Add support for property overrides in IndexTool > --- > > Key: PHOENIX-5867 > URL: https://issues.apache.org/jira/browse/PHOENIX-5867 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5867-4.x.001.patch, PHOENIX-5867-4.x.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Add support to accept property overrides in the form of -Dproperty=value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5867) Add support for property overrides in IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5867: Attachment: PHOENIX-5867-4.x.patch > Add support for property overrides in IndexTool > --- > > Key: PHOENIX-5867 > URL: https://issues.apache.org/jira/browse/PHOENIX-5867 > Project: Phoenix > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5867-4.x.patch > > > Add support to accept property overrides in the form of -Dproperty=value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5867) Add support for property overrides in IndexTool
Abhishek Singh Chouhan created PHOENIX-5867: --- Summary: Add support for property overrides in IndexTool Key: PHOENIX-5867 URL: https://issues.apache.org/jira/browse/PHOENIX-5867 Project: Phoenix Issue Type: Improvement Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 5.1.0, 4.16.0 Add support to accept property overrides in the form of -Dproperty=value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5751: Attachment: PHOENIX-5751-master.001.patch > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.14.4 > > Attachments: PHOENIX-5751-4.14-HBase-1.3.patch, > PHOENIX-5751-4.14-HBase-1.3.patch, PHOENIX-5751-master.001.patch, > PHOENIX-5751-master.001.patch, PHOENIX-5751-master.patch > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5751: Attachment: PHOENIX-5751-master.001.patch > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.14.4 > > Attachments: PHOENIX-5751-4.14-HBase-1.3.patch, > PHOENIX-5751-4.14-HBase-1.3.patch, PHOENIX-5751-master.001.patch, > PHOENIX-5751-master.patch > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5751: Attachment: PHOENIX-5751-4.14-HBase-1.3.patch > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.14.4 > > Attachments: PHOENIX-5751-4.14-HBase-1.3.patch, > PHOENIX-5751-4.14-HBase-1.3.patch, PHOENIX-5751-master.patch > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5751: Attachment: PHOENIX-5751-master.patch > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.14.4 > > Attachments: PHOENIX-5751-4.14-HBase-1.3.patch, > PHOENIX-5751-master.patch > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5751: Attachment: PHOENIX-5751-4.14-HBase-1.3.patch > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1 > > Attachments: PHOENIX-5751-4.14-HBase-1.3.patch > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan reassigned PHOENIX-5751: --- Assignee: Abhishek Singh Chouhan (was: Swaroopa Kadam) > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1 > > Attachments: PHOENIX-5751-4.14-HBase-1.3.patch > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5751) Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables
[ https://issues.apache.org/jira/browse/PHOENIX-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5751: Summary: Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable data tables (was: Optimize localCache utilization in IndexUtil#isGlobalIndexCheckEnabled()) > Remove redundant IndexUtil#isGlobalIndexCheckEnabled() calls for immutable > data tables > -- > > Key: PHOENIX-5751 > URL: https://issues.apache.org/jira/browse/PHOENIX-5751 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Major > Fix For: 5.1.0, 4.15.1 > > > We don't need to add and check if globalIndexChecker is enabled on data table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5745) Fix QA false negatives
[ https://issues.apache.org/jira/browse/PHOENIX-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5745: Fix Version/s: 4.16.0 4.14.4 5.1.0 > Fix QA false negatives > -- > > Key: PHOENIX-5745 > URL: https://issues.apache.org/jira/browse/PHOENIX-5745 > Project: Phoenix > Issue Type: Bug >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5745-master.patch > > > Hadoop QA always returns a -1, despite having all the sub components green. > This is a side effect of PHOENIX-4153 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5745) Fix QA false negatives
[ https://issues.apache.org/jira/browse/PHOENIX-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5745: Attachment: PHOENIX-5745-master.patch > Fix QA false negatives > -- > > Key: PHOENIX-5745 > URL: https://issues.apache.org/jira/browse/PHOENIX-5745 > Project: Phoenix > Issue Type: Bug >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Attachments: PHOENIX-5745-master.patch > > > Hadoop QA always returns a -1, despite having all the sub components green. > This is a side effect of PHOENIX-4153 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5745) Fix QA false negatives
Abhishek Singh Chouhan created PHOENIX-5745: --- Summary: Fix QA false negatives Key: PHOENIX-5745 URL: https://issues.apache.org/jira/browse/PHOENIX-5745 Project: Phoenix Issue Type: Bug Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Hadoop QA always returns a -1, despite having all the sub components green. This is a side effect of PHOENIX-4153 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5737) Hadoop QA run says no tests even though there are added IT tests
[ https://issues.apache.org/jira/browse/PHOENIX-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5737: Fix Version/s: 4.16.0 4.14.4 4.15.1 > Hadoop QA run says no tests even though there are added IT tests > > > Key: PHOENIX-5737 > URL: https://issues.apache.org/jira/browse/PHOENIX-5737 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Minor > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5737.master.patch, PHOENIX-5737.master.v1.patch > > > Even though there are ITs added in the patch, Hadoop QA run complains about > not adding any new tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5529) Creating a grand-child view on a table with an index fails
[
https://issues.apache.org/jira/browse/PHOENIX-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Singh Chouhan updated PHOENIX-5529:
Fix Version/s: 4.16.0
4.14.4
> Creating a grand-child view on a table with an index fails
> --
>
> Key: PHOENIX-5529
> URL: https://issues.apache.org/jira/browse/PHOENIX-5529
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Chinmay Kulkarni
>Assignee: Abhishek Singh Chouhan
>Priority: Major
> Labels: phoenix-hardening
> Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0
>
> Attachments: PHOENIX-5529-master.001.patch, PHOENIX-5529-master.patch
>
>
> Steps to reproduce:
> * Build the latest Phoenix jar from the 4.x-HBase-1.3 branch.
> * Start HBase 1.3 server with above Phoenix jar in the classpath
> * Connect with a Phoenix client with above jar in classpath. From SQLLine:
> {code:sql}
> CREATE TABLE IF NOT EXISTS Z_BASE_TABLE (ID INTEGER NOT NULL PRIMARY KEY,
> HOST VARCHAR(10), FLAG BOOLEAN);
> CREATE VIEW Z_VIEW1 (col1 INTEGER, col2 INTEGER, col3 INTEGER, col4 INTEGER,
> col5 INTEGER) AS SELECT * FROM Z_BASE_TABLE WHERE ID>10;
> CREATE INDEX Z_INDEX ON Z_BASE_TABLE(HOST);
> CREATE VIEW GRAND_CHILD1 AS SELECT * FROM Z_VIEW1 WHERE col1 > 2;
> {code}
> The last step fails with the following exception:
> {code:java}
> Error: ERROR 504 (42703): Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> (state=42703,code=504)
> org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504 (42703):
> Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> at
> org.apache.phoenix.schema.PTableImpl.getColumnForColumnName(PTableImpl.java:1076)
> at
> org.apache.phoenix.compile.FromCompiler$SingleTableColumnResolver.resolveColumn(FromCompiler.java:528)
> at
> org.apache.phoenix.compile.ExpressionCompiler.resolveColumn(ExpressionCompiler.java:368)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.resolveColumn(WhereCompiler.java:191)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:177)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:164)
> at
> org.apache.phoenix.parse.ColumnParseNode.accept(ColumnParseNode.java:56)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.CastParseNode.accept(CastParseNode.java:60)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at
> org.apache.phoenix.parse.ComparisonParseNode.accept(ComparisonParseNode.java:45)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.AndParseNode.accept(AndParseNode.java:47)
> at
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:94)
> at
> org.apache.phoenix.util.IndexUtil.rewriteViewStatement(IndexUtil.java:549)
> at
> org.apache.phoenix.util.ViewUtil.addIndexesFromParent(ViewUtil.java:283)
> at
> org.apache.phoenix.util.ViewUtil.addDerivedColumnsAndIndexesFromParent(ViewUtil.java:531)
> at
> org.apache.phoenix.schema.MetaDataClient.addColumnsAndIndexesFromAncestors(MetaDataClient.java:859)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4456)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4452)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3004)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1049)
> at
> org.apache.phoenix.compile.CreateTableCompiler$1.execute(CreateTableCompiler.java:217)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:411)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:393)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:381)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1843)
> at sqlline.Commands.execute(Commands.java:814)
> at sqlline.Commands.sql(Commands.java:754)
> at sqlline.SqlLine.dispatch(SqlLine.java:646)
> at sqlline.SqlLine.begin(SqlLine.java:510)
> at sqlline.SqlLine.start(SqlLine.java:233)
> at sqlline.SqlLine.main(SqlLine.java:175)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5529) Creating a grand-child view on a table with an index fails
[
https://issues.apache.org/jira/browse/PHOENIX-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Singh Chouhan updated PHOENIX-5529:
Attachment: PHOENIX-5529-master.001.patch
> Creating a grand-child view on a table with an index fails
> --
>
> Key: PHOENIX-5529
> URL: https://issues.apache.org/jira/browse/PHOENIX-5529
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Chinmay Kulkarni
>Assignee: Abhishek Singh Chouhan
>Priority: Major
> Labels: phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5529-master.001.patch, PHOENIX-5529-master.patch
>
>
> Steps to reproduce:
> * Build the latest Phoenix jar from the 4.x-HBase-1.3 branch.
> * Start HBase 1.3 server with above Phoenix jar in the classpath
> * Connect with a Phoenix client with above jar in classpath. From SQLLine:
> {code:sql}
> CREATE TABLE IF NOT EXISTS Z_BASE_TABLE (ID INTEGER NOT NULL PRIMARY KEY,
> HOST VARCHAR(10), FLAG BOOLEAN);
> CREATE VIEW Z_VIEW1 (col1 INTEGER, col2 INTEGER, col3 INTEGER, col4 INTEGER,
> col5 INTEGER) AS SELECT * FROM Z_BASE_TABLE WHERE ID>10;
> CREATE INDEX Z_INDEX ON Z_BASE_TABLE(HOST);
> CREATE VIEW GRAND_CHILD1 AS SELECT * FROM Z_VIEW1 WHERE col1 > 2;
> {code}
> The last step fails with the following exception:
> {code:java}
> Error: ERROR 504 (42703): Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> (state=42703,code=504)
> org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504 (42703):
> Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> at
> org.apache.phoenix.schema.PTableImpl.getColumnForColumnName(PTableImpl.java:1076)
> at
> org.apache.phoenix.compile.FromCompiler$SingleTableColumnResolver.resolveColumn(FromCompiler.java:528)
> at
> org.apache.phoenix.compile.ExpressionCompiler.resolveColumn(ExpressionCompiler.java:368)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.resolveColumn(WhereCompiler.java:191)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:177)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:164)
> at
> org.apache.phoenix.parse.ColumnParseNode.accept(ColumnParseNode.java:56)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.CastParseNode.accept(CastParseNode.java:60)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at
> org.apache.phoenix.parse.ComparisonParseNode.accept(ComparisonParseNode.java:45)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.AndParseNode.accept(AndParseNode.java:47)
> at
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:94)
> at
> org.apache.phoenix.util.IndexUtil.rewriteViewStatement(IndexUtil.java:549)
> at
> org.apache.phoenix.util.ViewUtil.addIndexesFromParent(ViewUtil.java:283)
> at
> org.apache.phoenix.util.ViewUtil.addDerivedColumnsAndIndexesFromParent(ViewUtil.java:531)
> at
> org.apache.phoenix.schema.MetaDataClient.addColumnsAndIndexesFromAncestors(MetaDataClient.java:859)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4456)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4452)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3004)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1049)
> at
> org.apache.phoenix.compile.CreateTableCompiler$1.execute(CreateTableCompiler.java:217)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:411)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:393)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:381)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1843)
> at sqlline.Commands.execute(Commands.java:814)
> at sqlline.Commands.sql(Commands.java:754)
> at sqlline.SqlLine.dispatch(SqlLine.java:646)
> at sqlline.SqlLine.begin(SqlLine.java:510)
> at sqlline.SqlLine.start(SqlLine.java:233)
> at sqlline.SqlLine.main(SqlLine.java:175)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5529) Creating a grand-child view on a table with an index fails
[
https://issues.apache.org/jira/browse/PHOENIX-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Singh Chouhan updated PHOENIX-5529:
Attachment: PHOENIX-5529-master.patch
> Creating a grand-child view on a table with an index fails
> --
>
> Key: PHOENIX-5529
> URL: https://issues.apache.org/jira/browse/PHOENIX-5529
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Chinmay Kulkarni
>Assignee: Abhishek Singh Chouhan
>Priority: Major
> Labels: phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5529-master.patch
>
>
> Steps to reproduce:
> * Build the latest Phoenix jar from the 4.x-HBase-1.3 branch.
> * Start HBase 1.3 server with above Phoenix jar in the classpath
> * Connect with a Phoenix client with above jar in classpath. From SQLLine:
> {code:sql}
> CREATE TABLE IF NOT EXISTS Z_BASE_TABLE (ID INTEGER NOT NULL PRIMARY KEY,
> HOST VARCHAR(10), FLAG BOOLEAN);
> CREATE VIEW Z_VIEW1 (col1 INTEGER, col2 INTEGER, col3 INTEGER, col4 INTEGER,
> col5 INTEGER) AS SELECT * FROM Z_BASE_TABLE WHERE ID>10;
> CREATE INDEX Z_INDEX ON Z_BASE_TABLE(HOST);
> CREATE VIEW GRAND_CHILD1 AS SELECT * FROM Z_VIEW1 WHERE col1 > 2;
> {code}
> The last step fails with the following exception:
> {code:java}
> Error: ERROR 504 (42703): Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> (state=42703,code=504)
> org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504 (42703):
> Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> at
> org.apache.phoenix.schema.PTableImpl.getColumnForColumnName(PTableImpl.java:1076)
> at
> org.apache.phoenix.compile.FromCompiler$SingleTableColumnResolver.resolveColumn(FromCompiler.java:528)
> at
> org.apache.phoenix.compile.ExpressionCompiler.resolveColumn(ExpressionCompiler.java:368)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.resolveColumn(WhereCompiler.java:191)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:177)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:164)
> at
> org.apache.phoenix.parse.ColumnParseNode.accept(ColumnParseNode.java:56)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.CastParseNode.accept(CastParseNode.java:60)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at
> org.apache.phoenix.parse.ComparisonParseNode.accept(ComparisonParseNode.java:45)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.AndParseNode.accept(AndParseNode.java:47)
> at
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:94)
> at
> org.apache.phoenix.util.IndexUtil.rewriteViewStatement(IndexUtil.java:549)
> at
> org.apache.phoenix.util.ViewUtil.addIndexesFromParent(ViewUtil.java:283)
> at
> org.apache.phoenix.util.ViewUtil.addDerivedColumnsAndIndexesFromParent(ViewUtil.java:531)
> at
> org.apache.phoenix.schema.MetaDataClient.addColumnsAndIndexesFromAncestors(MetaDataClient.java:859)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4456)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4452)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3004)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1049)
> at
> org.apache.phoenix.compile.CreateTableCompiler$1.execute(CreateTableCompiler.java:217)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:411)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:393)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:381)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1843)
> at sqlline.Commands.execute(Commands.java:814)
> at sqlline.Commands.sql(Commands.java:754)
> at sqlline.SqlLine.dispatch(SqlLine.java:646)
> at sqlline.SqlLine.begin(SqlLine.java:510)
> at sqlline.SqlLine.start(SqlLine.java:233)
> at sqlline.SqlLine.main(SqlLine.java:175)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.3.001.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.001.patch, PHOENIX-5704-4.x-HBase-1.3.patch, > PHOENIX-5704-master.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-master.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.001.patch, PHOENIX-5704-4.x-HBase-1.3.patch, > PHOENIX-5704-master.patch, PHOENIX-5704-master.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-master.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.patch, PHOENIX-5704-master.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.3.001.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.patch > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: (was: PHOENIX-5704-4.x-HBase-1.5.patch) > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.3.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5703) Add MAVEN_HOME toPATH in jenkins build
[ https://issues.apache.org/jira/browse/PHOENIX-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5703: Fix Version/s: 4.16.0 4.14.4 4.15.1 5.1.0 > Add MAVEN_HOME toPATH in jenkins build > -- > > Key: PHOENIX-5703 > URL: https://issues.apache.org/jira/browse/PHOENIX-5703 > Project: Phoenix > Issue Type: Improvement >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5703.4.x-HBase-1.3.v1.patch, > PHOENIX-5703.4.x-HBase-1.4.v1.patch, PHOENIX-5703.4.x-HBase-1.5.v1.patch, > PHOENIX-5703.master.v1.patch, PHOENIX-5703.master.v2.patch > > > We need to add MAVEN_HOME to PATH in Jenkins build for us to be able to run > any mvn commands as part of any test -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.5.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.5.patch > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
Abhishek Singh Chouhan created PHOENIX-5704: --- Summary: Covered column updates are not generated for previously deleted data table row Key: PHOENIX-5704 URL: https://issues.apache.org/jira/browse/PHOENIX-5704 Project: Phoenix Issue Type: Bug Affects Versions: 4.14.3, 5.0.0, 4.15.0 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 5.1.0, 4.15.1, 4.14.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5529) Creating a grand-child view on a table with an index fails
[
https://issues.apache.org/jira/browse/PHOENIX-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Singh Chouhan reassigned PHOENIX-5529:
---
Assignee: Abhishek Singh Chouhan
> Creating a grand-child view on a table with an index fails
> --
>
> Key: PHOENIX-5529
> URL: https://issues.apache.org/jira/browse/PHOENIX-5529
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Chinmay Kulkarni
>Assignee: Abhishek Singh Chouhan
>Priority: Major
> Labels: phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
>
> Steps to reproduce:
> * Build the latest Phoenix jar from the 4.x-HBase-1.3 branch.
> * Start HBase 1.3 server with above Phoenix jar in the classpath
> * Connect with a Phoenix client with above jar in classpath. From SQLLine:
> {code:sql}
> CREATE TABLE IF NOT EXISTS Z_BASE_TABLE (ID INTEGER NOT NULL PRIMARY KEY,
> HOST VARCHAR(10), FLAG BOOLEAN);
> CREATE VIEW Z_VIEW1 (col1 INTEGER, col2 INTEGER, col3 INTEGER, col4 INTEGER,
> col5 INTEGER) AS SELECT * FROM Z_BASE_TABLE WHERE ID>10;
> CREATE INDEX Z_INDEX ON Z_BASE_TABLE(HOST);
> CREATE VIEW GRAND_CHILD1 AS SELECT * FROM Z_VIEW1 WHERE col1 > 2;
> {code}
> The last step fails with the following exception:
> {code:java}
> Error: ERROR 504 (42703): Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> (state=42703,code=504)
> org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504 (42703):
> Undefined column. columnName=Z_VIEW1#Z_INDEX.0:COL1
> at
> org.apache.phoenix.schema.PTableImpl.getColumnForColumnName(PTableImpl.java:1076)
> at
> org.apache.phoenix.compile.FromCompiler$SingleTableColumnResolver.resolveColumn(FromCompiler.java:528)
> at
> org.apache.phoenix.compile.ExpressionCompiler.resolveColumn(ExpressionCompiler.java:368)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.resolveColumn(WhereCompiler.java:191)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:177)
> at
> org.apache.phoenix.compile.WhereCompiler$WhereExpressionCompiler.visit(WhereCompiler.java:164)
> at
> org.apache.phoenix.parse.ColumnParseNode.accept(ColumnParseNode.java:56)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.CastParseNode.accept(CastParseNode.java:60)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at
> org.apache.phoenix.parse.ComparisonParseNode.accept(ComparisonParseNode.java:45)
> at
> org.apache.phoenix.parse.CompoundParseNode.acceptChildren(CompoundParseNode.java:64)
> at org.apache.phoenix.parse.AndParseNode.accept(AndParseNode.java:47)
> at
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:94)
> at
> org.apache.phoenix.util.IndexUtil.rewriteViewStatement(IndexUtil.java:549)
> at
> org.apache.phoenix.util.ViewUtil.addIndexesFromParent(ViewUtil.java:283)
> at
> org.apache.phoenix.util.ViewUtil.addDerivedColumnsAndIndexesFromParent(ViewUtil.java:531)
> at
> org.apache.phoenix.schema.MetaDataClient.addColumnsAndIndexesFromAncestors(MetaDataClient.java:859)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4456)
> at
> org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4452)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3004)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1049)
> at
> org.apache.phoenix.compile.CreateTableCompiler$1.execute(CreateTableCompiler.java:217)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:411)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:393)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:381)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1843)
> at sqlline.Commands.execute(Commands.java:814)
> at sqlline.Commands.sql(Commands.java:754)
> at sqlline.SqlLine.dispatch(SqlLine.java:646)
> at sqlline.SqlLine.begin(SqlLine.java:510)
> at sqlline.SqlLine.start(SqlLine.java:233)
> at sqlline.SqlLine.main(SqlLine.java:175)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Fix Version/s: (was: 4.15.1) 4.14.4 > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.002.patch, > PHOENIX-5676-4.x-HBase-1.5.patch, PHOENIX-5676-4.x-HBase-1.5.patch, > PHOENIX-5676-master.002.patch, PHOENIX-5676-master.patch > > Time Spent: 2h 40m > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Attachment: PHOENIX-5676-master.002.patch > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.002.patch, > PHOENIX-5676-4.x-HBase-1.5.patch, PHOENIX-5676-4.x-HBase-1.5.patch, > PHOENIX-5676-master.002.patch, PHOENIX-5676-master.patch > > Time Spent: 2h 40m > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Attachment: PHOENIX-5676-4.x-HBase-1.5.002.patch > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.002.patch, > PHOENIX-5676-4.x-HBase-1.5.patch, PHOENIX-5676-4.x-HBase-1.5.patch, > PHOENIX-5676-master.patch > > Time Spent: 2h 40m > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5673) The mutation state is silently getting cleared on the execution of any DDL
[
https://issues.apache.org/jira/browse/PHOENIX-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Singh Chouhan updated PHOENIX-5673:
Priority: Critical (was: Major)
> The mutation state is silently getting cleared on the execution of any DDL
> --
>
> Key: PHOENIX-5673
> URL: https://issues.apache.org/jira/browse/PHOENIX-5673
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: Sandeep Guggilam
>Priority: Critical
> Labels: beginner, newbie
> Fix For: 4.16.0
>
>
> When we execute any DDL statement, the mutations state is rolled back
> silently without informing the user. It should probably throw an exception
> saying that the mutation state is not empty when executing any DDL. See the
> below example:
>
> Steps to reproduce:
> create table t1 (pk varchar not null primary key, mycol varchar)
> upsert into t1 (pk, mycol) values ('x','x');
> create table t2 (pk varchar not null primary key, mycol varchar)
> When we try to execute the above statements and do a conn.commit() at the
> end, it would silently rollback the upsert statement when we execute the
> second create statement and you wouldn't see the ('x', 'x') values in the
> first table. Instead it should probably throw an exception saying that the
> mutation state is not empty
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Attachment: PHOENIX-5676-4.x-HBase-1.5.patch > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.patch, > PHOENIX-5676-4.x-HBase-1.5.patch, PHOENIX-5676-master.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Fix Version/s: 5.1.0 > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.patch, > PHOENIX-5676-master.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Attachment: PHOENIX-5676-master.patch > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.15.1, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.patch, > PHOENIX-5676-master.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5676) Inline-verification from IndexTool does not handle TTL/row-expiry
[ https://issues.apache.org/jira/browse/PHOENIX-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5676: Attachment: PHOENIX-5676-4.x-HBase-1.5.patch > Inline-verification from IndexTool does not handle TTL/row-expiry > - > > Key: PHOENIX-5676 > URL: https://issues.apache.org/jira/browse/PHOENIX-5676 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.14.3 >Reporter: Priyank Porwal >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.15.1, 4.16.0 > > Attachments: PHOENIX-5676-4.x-HBase-1.5.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when > we run IndexTool with verification on such tables and it's indexes, rows that > are near expiry will successfully get rebuilt, but may not be returned on > verification read due to expiry. This will result in index verification > problem and may also fail rebuild job. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5628) Phoenix Function to Return HBase Row Key of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5628: Attachment: PHOENIX-5628-master.001.patch > Phoenix Function to Return HBase Row Key of Column Cell > --- > > Key: PHOENIX-5628 > URL: https://issues.apache.org/jira/browse/PHOENIX-5628 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5628-4.x-HBase-1.5.patch, > PHOENIX-5628-master.001.patch, PHOENIX-5628-master.patch > > > It's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the byte array of a row key that corresponds to a cell with a > Phoenix query. This can then be looked up in the HBase shell. > For example: > SELECT ROWKEY_BYTES(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5628) Phoenix Function to Return HBase Row Key of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5628: Attachment: PHOENIX-5628-4.x-HBase-1.5.patch > Phoenix Function to Return HBase Row Key of Column Cell > --- > > Key: PHOENIX-5628 > URL: https://issues.apache.org/jira/browse/PHOENIX-5628 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5628-4.x-HBase-1.5.patch, > PHOENIX-5628-master.patch > > > It's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the byte array of a row key that corresponds to a cell with a > Phoenix query. This can then be looked up in the HBase shell. > For example: > SELECT ROWKEY_BYTES(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5629) Phoenix Function to Return HBase Timestamp of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5629: Attachment: (was: PHOENIX-5628-master.patch) > Phoenix Function to Return HBase Timestamp of Column Cell > - > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5629) Phoenix Function to Return HBase Timestamp of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5629: Attachment: (was: PHOENIX-5628-4.x-HBase-1.5.patch) > Phoenix Function to Return HBase Timestamp of Column Cell > - > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5628) Phoenix Function to Return HBase Row Key of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan reassigned PHOENIX-5628: --- Assignee: Abhishek Singh Chouhan > Phoenix Function to Return HBase Row Key of Column Cell > --- > > Key: PHOENIX-5628 > URL: https://issues.apache.org/jira/browse/PHOENIX-5628 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Attachments: PHOENIX-5628-master.patch > > > It's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the byte array of a row key that corresponds to a cell with a > Phoenix query. This can then be looked up in the HBase shell. > For example: > SELECT ROWKEY_BYTES(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5628) Phoenix Function to Return HBase Row Key of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5628: Attachment: PHOENIX-5628-master.patch > Phoenix Function to Return HBase Row Key of Column Cell > --- > > Key: PHOENIX-5628 > URL: https://issues.apache.org/jira/browse/PHOENIX-5628 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Attachments: PHOENIX-5628-master.patch > > > It's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the byte array of a row key that corresponds to a cell with a > Phoenix query. This can then be looked up in the HBase shell. > For example: > SELECT ROWKEY_BYTES(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5629) Phoenix Function to Return HBase Timestamp of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5629: Attachment: PHOENIX-5628-master.patch > Phoenix Function to Return HBase Timestamp of Column Cell > - > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5628-4.x-HBase-1.5.patch, > PHOENIX-5628-master.patch > > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5629) Phoenix Function to Return HBase Timestamp of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5629: Attachment: PHOENIX-5628-4.x-HBase-1.5.patch > Phoenix Function to Return HBase Timestamp of Column Cell > - > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > Attachments: PHOENIX-5628-4.x-HBase-1.5.patch > > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5629) Phoenix Function to Return HBase Timestamp of Column Cell
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan reassigned PHOENIX-5629: --- Assignee: Abhishek Singh Chouhan > Phoenix Function to Return HBase Timestamp of Column Cell > - > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Abhishek Singh Chouhan >Priority: Major > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5637) Queries with SCN return expired rows
[ https://issues.apache.org/jira/browse/PHOENIX-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5637: Fix Version/s: (was: 5.1.0) 4.16.0 > Queries with SCN return expired rows > > > Key: PHOENIX-5637 > URL: https://issues.apache.org/jira/browse/PHOENIX-5637 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5637-4.x-HBase-1.5.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5637) Queries with SCN return expired rows
[ https://issues.apache.org/jira/browse/PHOENIX-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5637: Issue Type: Bug (was: Task) > Queries with SCN return expired rows > > > Key: PHOENIX-5637 > URL: https://issues.apache.org/jira/browse/PHOENIX-5637 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.15.1, 4.14.4 > > Attachments: PHOENIX-5637-4.x-HBase-1.5.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5637) Queries with SCN return expired rows
[ https://issues.apache.org/jira/browse/PHOENIX-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5637: Attachment: PHOENIX-5637-4.x-HBase-1.5.patch > Queries with SCN return expired rows > > > Key: PHOENIX-5637 > URL: https://issues.apache.org/jira/browse/PHOENIX-5637 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.14.4 > > Attachments: PHOENIX-5637-4.x-HBase-1.5.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5637) Queries with SCN return expired rows
Abhishek Singh Chouhan created PHOENIX-5637: --- Summary: Queries with SCN return expired rows Key: PHOENIX-5637 URL: https://issues.apache.org/jira/browse/PHOENIX-5637 Project: Phoenix Issue Type: Task Affects Versions: 4.14.3 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Fix For: 4.14.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5254) Broken Link to Installation Section of the Download Page
[ https://issues.apache.org/jira/browse/PHOENIX-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5254: Labels: website (was: ) > Broken Link to Installation Section of the Download Page > > > Key: PHOENIX-5254 > URL: https://issues.apache.org/jira/browse/PHOENIX-5254 > Project: Phoenix > Issue Type: Bug >Reporter: William Shen >Assignee: Xinyi Yan >Priority: Minor > Labels: website > Attachments: PHOENIX-5254.patch > > > In https://phoenix.apache.org/Phoenix-in-15-minutes-or-less.html, we > reference https://phoenix.apache.org/download.html#Installation for > installation instruction. However, the section does not exist on the download > page. The installation instruction is actually at > https://phoenix.apache.org/installation.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5203) Update contributing guidelines on Phoenix website
[ https://issues.apache.org/jira/browse/PHOENIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5203: Priority: Trivial (was: Major) > Update contributing guidelines on Phoenix website > - > > Key: PHOENIX-5203 > URL: https://issues.apache.org/jira/browse/PHOENIX-5203 > Project: Phoenix > Issue Type: Improvement >Reporter: Karan Mehta >Assignee: Swaroopa Kadam >Priority: Trivial > Attachments: PHOENIX-5203.master.v1.patch, > PHOENIX-5203.master.v2.patch, PHOENIX-5203.master.v3.patch > > > Add details about patch file naming convention, assumption that patch files > only work if it contains single commit in them (for Hadoop QA) and asking > users to raise PR's as well along with patch files since it makes it easier > for others to review. This will help improve onboarding. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
