[
https://issues.apache.org/jira/browse/PHOENIX-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133689#comment-15133689
]
Thomas D'Silva commented on PHOENIX-2605:
-----------------------------------------
I think we have the same issue for the regular UPSERT SELECT index build as
well. Even though we set the max timestamp of the scan, TransactionProcessor
kicks in and modifies the timestamps based on the transaction.
> Enhance IndexToolIT to test transactional tables
> ------------------------------------------------
>
> Key: PHOENIX-2605
> URL: https://issues.apache.org/jira/browse/PHOENIX-2605
> Project: Phoenix
> Issue Type: Test
> Reporter: Thomas D'Silva
> Assignee: Thomas D'Silva
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2605.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
