[
https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832790#comment-16832790
]
Kadir OZDEMIR commented on PHOENIX-5156:
----------------------------------------
[~tdsilva], No, the previous implementations will be replaced. So, the users
will be implicitly switched to the new implementation. Please note this Jira
covers the mutable indexes. The read paths for mutable and immutable are
common. So, it also covers the read path for immutable indexes. I have created
a separate Jira (PHOENIX-5211) for immutable global indexes to implement the
remaining work for immutable 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, 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: 18h 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)
