[
https://issues.apache.org/jira/browse/PHOENIX-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577147#comment-17577147
]
Istvan Toth commented on PHOENIX-6627:
--------------------------------------
{quote}Can Tephra and its libthrift dependency (0.9.x has a high scoring CVE
associated with it) simply be unconditionally removed? The TEPHRA enum value
would remain for compatibility as the current patch provides, but the Tephra
transaction manager class and the Tephra coprocessor classes could be deleted,
and the no-op transaction manager should be patched so the coprocessor name and
capabilities getters return null rather than throw an
UnsupportedOperationException.
{quote}
I agree on keeping (but preferable renaming) the enum value.
Come to think of it, we cannot just remove the Tephra coprocessor, we MUST keep
it, otherwise the RS is just going to fail to start up after an upgrade.
> Remove all references to Tephra from 4.x and master
> ---------------------------------------------------
>
> Key: PHOENIX-6627
> URL: https://issues.apache.org/jira/browse/PHOENIX-6627
> Project: Phoenix
> Issue Type: Sub-task
> Components: 4.x, tephra
> Reporter: Istvan Toth
> Assignee: Zsolt Gyulavari
> Priority: Major
> Fix For: 5.2.0
>
>
> Removing tephra from the runtime is easy, as it uses the well defind
> TransactionProvider interfaces.
> Removing Tephra references from all the test cases is a much bigger task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
