[
https://issues.apache.org/jira/browse/PHOENIX-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868822#comment-15868822
]
Poorna Chandra commented on PHOENIX-3585:
-----------------------------------------
[~tdsilva] Does IndexHalfStoreFileReaderGenerator work on transactional data?
If so invalid transaction pruning will complicate the things a little bit. In
the postCompact hook, TransactionProcessor records the prune upper bound for
every region. If some store files containing transactional data of a region are
not compacted when the postCompact hook runs, then it will lead to
inconsistency. It may be better to disable compaction completely when splits
and merges happen like [~rajeshbabu] suggested. We could override
TransactionProcessor methods in PhoenixTransactionalProcessor to achieve this.
> MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail
> for transactional tables and local indexes
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3585
> URL: https://issues.apache.org/jira/browse/PHOENIX-3585
> Project: Phoenix
> Issue Type: Bug
> Reporter: Thomas D'Silva
> Assignee: Thomas D'Silva
> Attachments: diff.patch
>
>
> the tests fail if we use HDFSTransactionStateStorage instead of
> InMemoryTransactionStateStorage when we create the TransactionManager in
> BaseTest
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
