[
https://issues.apache.org/jira/browse/PHOENIX-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578548#comment-17578548
]
ASF GitHub Bot commented on PHOENIX-6627:
-----------------------------------------
apurtell opened a new pull request, #1486:
URL: https://github.com/apache/phoenix/pull/1486
Retire Tephra.
Considerations:
Ordinals of `TransactionFactory.Provider` are maintained to preserve
compatibility with deployed system catalogs. The enum label for the former
Tephra provider is deliberately renamed to `NOTAVAILABLE` so any downstreams
with ill-advised direct dependencies on it will fail to compile.
A coprocessor named `TephraTransactionalProcessor` is retained, with a no-op
implementation, to prevent regionserver aborts in the worst case that a Tephra
table remains deployed and the table coprocessor list has not changed. This
should not happen. Users should be provided a migration runbook.
The `commitDDLFence` phase of `MutationState` is retained although it may no
longer be necessary. Recommend a follow up issue.
`PhoenixTransactionContext.PROPERTY_TTL` is retained. It is possible a
future txn engine option will have a similar design feature and will need to
alter cell timestamps. Recommend a follow up issue.
`storeNulls` for transactional tables remains enabled for compatibility. It
is possible a future txn engine option will have a similar design feature and
will need to manage tombstones in a non-default way. Recommend a follow up
issue.
Requests to ALTER a table from transactional to non transactional are still
rejected. It is very likely OMID has similar complex state cleanup and removal
requirements, and txn engines in general are likely to have this class of
problem.
> 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: Andrew Kyle Purtell
> 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)
