[
https://issues.apache.org/jira/browse/PHOENIX-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557037#comment-17557037
]
ASF GitHub Bot commented on PHOENIX-6627:
-----------------------------------------
gjacoby126 commented on PR #1455:
URL: https://github.com/apache/phoenix/pull/1455#issuecomment-1162115749
@stoty - so long as the region comes online, I like the idea of the coproc
just sending a clear, non-retriable exception if tephra is enabled on a region.
(If the region crashes, then there's a risk of it taking down the entire
cluster as the HMaster keeps trying to bring it up on other RSs, killing each
one.)
And no, I've never seen a live Tephra use case in production.
> 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
>
> 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.7#820007)
