[
https://issues.apache.org/jira/browse/PHOENIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696028#comment-17696028
]
Istvan Toth commented on PHOENIX-6283:
--------------------------------------
This is not strictly true [~kadir] .
Transactional non-tx tables using the new indexing do not need the feature.
However, we should consider the upgrade path, where a user is upgrading from a
pre 5.1 / 4.16 version, and has not coverted to the new indexing yet.
If the table is using the old indexing, then we should keep the current
behaviour, and preferably keep the test for it (converting the test table to
use the old indexing).
Maybe moving the coprocessor hook providing this functionality into the old
indexing coprocessor would work ?
> MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase
> 2.3
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-6283
> URL: https://issues.apache.org/jira/browse/PHOENIX-6283
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Blocker
> Fix For: 5.1.0, 4.16.0
>
>
> This seems to be related to the Indexing rebase.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
