You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2021/01/15 12:10:00 UTC
[jira] [Updated] (PHOENIX-5768) Supporting partial overwrites for
immutable tables with indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth updated PHOENIX-5768:
---------------------------------
Fix Version/s: 5.1.0
> Supporting partial overwrites for immutable tables with indexes
> ---------------------------------------------------------------
>
> Key: PHOENIX-5768
> URL: https://issues.apache.org/jira/browse/PHOENIX-5768
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Critical
> Fix For: 5.1.0
>
> Attachments: PHOENIX-5678.master.001.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Phoenix allows immutable table with indexes to be overwritten partially as long as the indexed columns are not updated during partial overwrites. However, there is no check/enforcement for this. The immutable index mutations are prepared on the client side without reading the existing data table rows. This means the index mutations prepared by the client will be partial when the data table row mutations are partial. The new indexing design assumes index rows are always full and all cells within an index row have the same timestamp. On the read path, GlobalIndexChecker returns only the cells with the most recent timestamp of the row. This means that if the client updates the same row multiple times, the client will read back only the most recent update which could be partial.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)