[jira] [Commented] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

["Vincent Poon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003653#comment-16003653 ] 

Vincent Poon commented on PHOENIX-3825:
---------------------------------------

[~jamestaylor]  Any idea what this method is for?
IndexUpdateManager#fixUpCurrentUpdates(..)

When I comment out all but the last line of that method, this JIRA is fixed, and the normal index updates seem to work as well.

But that method seems to be there for a reason.  From what I can tell, it's trying to do the opposite of this JIRA (but I could be wrong).  It seems like it's trying to avoid unnecessary index writes.  If there are index mutations that are covered/hidden by the current index mutation, then they are marked for removal from the batch of index updates.  That way, only the final visible mutation is written.

What do you think is the correct behavior here?  Write all versions, or only the latest?

> Mutable Index rebuild does not write an index version for each data row version
> -------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3825
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3825
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Vincent Poon
>
> 1) Write a row
> 2) Disable the index
> 3) write a series of updates to the data row
> 4) trigger the BuildIndexScheduleTask partial rebuild
> The index table will only have 1 new version, whereas the data row had many versions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)