[
https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832105#comment-16832105
]
Thomas D'Silva commented on PHOENIX-5156:
-----------------------------------------
Sorry [~kozdemir] I haven't reviewed the patch in detail, but just an overall
question. With this change does would the previous implementation of our
immutable and mutable global indexes be supported, or would users have to
switch the this new implementation ?
> 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: 14.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)
