[
https://issues.apache.org/jira/browse/PHOENIX-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133487#comment-15133487
]
James Taylor edited comment on PHOENIX-2605 at 2/5/16 1:55 AM:
---------------------------------------------------------------
One issue with the IndexToolIT usage will be the timestamp used by the
transaction manager. We really need it to be at the point when the index was
created. Ideally what we'd want to do is add the TransactionVisibilityFilter
and set the min/max timestamp ourselves (multiplying the SCN by 1,000,000 using
our util function). You could start a transaction and get the in-flight and
invalid transaction information from that.
Another easier, but somewhat hackier approach would be to have a new scan
attribute like TX_SCN and set the upper bound of the scan time range to this
value in BaseScannerRegionObserver.preScannerOpen() which would fire after the
Tephra TransactionProcessor so it could override the time range.
was (Author: jamestaylor):
One issue with the IndexToolIT usage will be the timestamp used by the
transaction manager. We really need it to be at the point when the index was
created. Ideally what we'd want to do is add the TransactionVisibilityFilter
and set the min/max timestamp ourselves (multiplying the SCN by 1,000,000 using
our util function). You could start a transaction and get the in-flight and
invalid transaction information from that.
> 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)
