[
https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884057#comment-17884057
]
Kadir Ozdemir commented on PHOENIX-5156:
----------------------------------------
[~filtertip], I am sorry for my way delayed response. I just noticed this. Yes,
a read and write happen on the same row concurrently, the read would possible
get an unverified row and then go through the repair process. I do not see this
is an indexing issue. It is the issue that we do not provide snapshot isolation
for our scans, that is, not setting time range for them. I am planning to add
this to Phoenix in general such that a scan should not see mutations that are
added after the query is executed, that is the result set is created (before
the next() call). This will practically eliminate this issue.
> 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
(v8.20.10#820010)
