[
https://issues.apache.org/jira/browse/PHOENIX-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766678#comment-16766678
]
Kadir OZDEMIR commented on PHOENIX-5019:
----------------------------------------
The fix for PHOENIX-5018 will also fix this issue.
> Index mutations created by synchronous index builds will have wrong timestamps
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-5019
> URL: https://issues.apache.org/jira/browse/PHOENIX-5019
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.14.1
> Reporter: Vincent Poon
> Assignee: Kadir OZDEMIR
> Priority: Major
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
