[
https://issues.apache.org/jira/browse/PHOENIX-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577049#comment-17577049
]
Andrew Kyle Purtell edited comment on PHOENIX-6627 at 8/9/22 12:06 AM:
-----------------------------------------------------------------------
[~gyzsolt] [~stoty] [~gjacoby]
Is see PR #1455 has been in draft state for a while. Is this still being
actively worked on? Do you need someone else to pick it up? I volunteer for
that if so.
Also wondering if backwards support is really needed given this:
bq. And no, I've never seen a live Tephra use case in production.
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.
was (Author: apurtell):
[~gyzsolt] [~stoty] [~gjacoby]
Is see PR #1455 has been in draft state for a while. Is this still being
actively worked on? Do you need someone else to pick it up? I volunteer for
that if so.
Also wondering if backwards support is really needed given this:
bq. And no, I've never seen a live Tephra use case in production.
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 should be removed,
and the no-op transaction manager should be patched so the coprocessor name and
capabilities getters return null rather than throw an
UnsupportedOperationException.
> 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)
