[PHOENIX-5019] Index mutations created by synchronous index builds will have wrong timestamps

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Resolved
• Affects Version/s: 5.0.0, 4.14.1
• Assignee: Kadir OZDEMIR
• Reporter: Vincent Poon
• Created: 14/Nov/18 18:59
• Updated: 22/Feb/19 19:28
• Resolved: 22/Feb/19 19:28

Description

Similar to PHOENIX-5018, if we do a synchronous index build, since it's doing an UpsertSelect , the timestamp of an index mutation will have current wallclock time instead matching up with the data table counterpart's timestamp

Issue Links

• is related to: PHOENIX-5018 Index mutations created by UPSERT SELECT will have wrong timestamps