[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5156: Fix Version/s: 4.14.3 > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.005.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.019.patch, > PHOENIX-5156.master.021.patch, PHOENIX-5156.master.022.patch > > Time Spent: 31h 10m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5156: --- Fix Version/s: 5.1.0 4.15.0 > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.005.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.019.patch, > PHOENIX-5156.master.021.patch, PHOENIX-5156.master.022.patch > > Time Spent: 31h 10m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.4.x-HBase-1.4.005.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.005.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.019.patch, > PHOENIX-5156.master.021.patch, PHOENIX-5156.master.022.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.022.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.019.patch, PHOENIX-5156.master.021.patch, > PHOENIX-5156.master.022.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: (was: PHOENIX-5156.master.018.patch) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.019.patch, PHOENIX-5156.master.021.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.021.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.019.patch, PHOENIX-5156.master.021.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: (was: PHOENIX-5156.4.x-HBase-1.4.003.patch) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.019.patch, PHOENIX-5156.master.021.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: (was: PHOENIX-5156.master.020.patch) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.018.patch, PHOENIX-5156.master.019.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.4.x-HBase-1.4.003.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.003.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.018.patch, > PHOENIX-5156.master.019.patch, PHOENIX-5156.master.020.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: (was: PHOENIX-5156.4.x-HBase-1.4.003.patch) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.018.patch, PHOENIX-5156.master.019.patch, > PHOENIX-5156.master.020.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: (was: PHOENIX-5156.master.020.patch) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.003.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.018.patch, > PHOENIX-5156.master.019.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.4.x-HBase-1.4.003.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.003.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.018.patch, > PHOENIX-5156.master.019.patch, PHOENIX-5156.master.020.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.020.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.018.patch, PHOENIX-5156.master.019.patch, > PHOENIX-5156.master.020.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokcen Iskender updated PHOENIX-5156: - Attachment: PHOENIX-5156.master.019.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.018.patch, PHOENIX-5156.master.019.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.018.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, > PHOENIX-5156.master.018.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.4.x-HBase-1.4.002.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch, PHOENIX-5156.master.013.patch, > PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch, > PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.017.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch > > Time Spent: 31h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.016.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch > > Time Spent: 28h 40m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.015.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch > > Time Spent: 26h 40m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.014.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch > > Time Spent: 21h 50m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.013.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch > > Time Spent: 21h 50m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.4.x-HBase-1.4.001.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch > > Time Spent: 18.5h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.012.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, > PHOENIX-5156.master.012.patch > > Time Spent: 18.5h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.011.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch > > Time Spent: 18.5h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.010.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch, > PHOENIX-5156.master.010.patch > > Time Spent: 12.5h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.009.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch > > Time Spent: 8h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.008.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch, > PHOENIX-5156.master.008.patch > > Time Spent: 8h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.007.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch, PHOENIX-5156.master.007.patch > > Time Spent: 6h > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.006.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, > PHOENIX-5156.master.006.patch > > Time Spent: 5h 40m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Attachment: PHOENIX-5156.master.005.patch > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch > > Time Spent: 5h 40m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Description: Without transactional tables, the mutable global indexes can get easily out of sync with their data tables in Phoenix. Transactional tables require a separate transaction manager, have some restrictions and performance penalties. This issue is to have consistent mutable global indexes without the need for using transactional tables. (was: Without transactional tables, the global indexes can get easily out of sync with their data tables in Phoenix. Transactional tables require a separate transaction manager, have some restrictions and performance penalties. This issue is to have consistent global indexes without the need for using transactional tables.) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch > > Time Spent: 4h 20m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR updated PHOENIX-5156: --- Summary: Consistent Mutable Global Indexes for Non-Transactional Tables (was: Consistent Global Indexes for Non-Transactional Tables) > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Attachments: PHOENIX-5156.master.001.patch, > PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch, > PHOENIX-5156.master.004.patch > > Time Spent: 4h 20m > Remaining Estimate: 0h > > Without transactional tables, the global indexes can get easily out of sync > with their data tables in Phoenix. Transactional tables require a separate > transaction manager, have some restrictions and performance penalties. This > issue is to have consistent global indexes without the need for using > transactional tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
