[
https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Poon reassigned PHOENIX-3825:
-------------------------------------
Assignee: Vincent Poon
Affects Version/s: 4.11.0
4.10.0
As I was fixing the integration tests, I realized fixUpCurrentUpdates is also
used for out-of-order updates. The logic is arguably too complicated to handle
that case, and I started refactoring but it was looking like a pretty big code
change.
I think the simplest fix for now is to check for "ignoreNewerMutations", which
is true when replaying for partial rebuilds. In that case, we skip that
method, and all the index versions get created appropriately. I added a unit
test for that so we don't regress.
> 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
> Affects Versions: 4.10.0, 4.11.0
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Attachments: PHOENIX-3825.master.v1.patch
>
>
> 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)
