You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Kadir OZDEMIR (JIRA)" <ji...@apache.org> on 2019/03/25 20:03:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16801015#comment-16801015 ]
Kadir OZDEMIR commented on PHOENIX-5156:
----------------------------------------
I have created a separate Jira (PHOENIX-5211) for immutable global indexes so that this Jira (PHOENIX-5156) can focus on only mutable global indexes.
> 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)