Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Normal
Description
In SecondaryIndexManager.onUpdated(), we fail to copy the DeletionInfo from the existing and new rows before notifying the index of the update. This leads the index to believe a new, live row has been inserted instead of a single-row deletion. It looks like this has been a problem since 3.0.0-beta1.
I've attached a simple patch that fixes the issue. I'm working on a full patch with tests, etc.