[
https://issues.apache.org/jira/browse/PHOENIX-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578163#comment-17578163
]
Andrew Kyle Purtell edited comment on PHOENIX-6627 at 8/10/22 9:51 PM:
-----------------------------------------------------------------------
Anyone who has deployed Tephra transitional tables, if such a user actually
exists, would be at a dead end?
MetaDataClient does not allow going from transactional to non transactional.
This is discussed there in some comments that describe how for Tephra tables
all cell timestamps would need to be rewritten and Tephra-specific delete
markers would need to be removed or concerted into normal tombstones to process
such an ALTER. I think it is probably out of scope of a "remove" JIRA to try
and implement complex one-off functionality, especially for an option suspected
of never being deployed, but want to raise the issue.
ALTER of an OMID transactional to nontransactional table would be problematic
for broadly similar reasons. All of the shadow metadata should be discarded.
Any txn engine is likely to have this general class of problem.
What would you recommend to users? "Before upgrading, if you have a Tephra
transactional table, first run a table export operation. Then drop the table.
Then upgrade. Then create a replacement table. Then import table data from the
earlier export." ?
[~stoty] [~gjacoby] [~kadir] [~jisaac]
was (Author: apurtell):
Anyone who has deployed Tephra transitional tables, if such a user actually
exists, would be at a dead end?
MetaDataClient does not allow going from transactional to non transactional.
This is mentioned in comments that describe how for Tephra tables all cell
timestamps would need to be rewritten and Tephra-specific delete markers would
need to be removed or concerted into normal tombstones to process such an
ALTER. I think it is probably out of scope of a "remove" JIRA to try and
implement complex one-off functionality, especially for an option suspected of
never being deployed, but want to raise the issue.
ALTER of an OMID transactional to nontransactional table would be problematic
for broadly similar reasons. All of the shadow metadata should be discarded.
Any txn engine is likely to have this general class of problem.
What would you recommend to users? "Before upgrading, if you have a Tephra
transactional table, first run a table export operation. Then drop the table.
Then upgrade. Then create a replacement table. Then import table data from the
earlier export." ?
[~stoty] [~gjacoby] [~kadir] [~jisaac]
> 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)
