[
https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003801#comment-16003801
]
James Taylor commented on PHOENIX-3825:
---------------------------------------
IMHO, we should write an index row for each version, otherwise point-in-time
queries wouldn't work correctly. If you remove the
IndexUpdateManager#fixUpCurrentUpdates call, do the unit tests pass (excluding
TestIndexUpdateManager)? Perhaps we can add a point in time query unit test
that relies on the new behavior so it won't regress (and update
TestIndexUpdateManager).
> 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)
