[
https://issues.apache.org/jira/browse/PHOENIX-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463376#comment-17463376
]
Lars Hofhansl commented on PHOENIX-6615:
----------------------------------------
Thanks [~stoty] .
I agree the bitrot is around Tephra, not Phoenix. And the job you do
maintaining Tephra is appreciated!
Omid and Tephra have different pros and cons. Tephra has no (or negligible) per
row cost, but a higher per transaction cost (since all failed or rolled-back
transactions have to be sent to all future transaction until they are
collected), Omid on the other hand has a fairly high per row cost (as the
shadow columns need to be updated) but no lasting per transactions cost (once
the shadow columns are updated no further information is needed).
So I'd use Omid for many small transactions, and Tephra for few but large
transactions... And maybe it's really not worth it. :)
I agree with you that maintaining the perception that a project is maintained
is worth than ripping it out.
As for transactions in general... Phoenix is the only engine I know that
supports OLTP like interactions (JDBC et al), and high-volume interactions (via
regions, guideposts and M/R, Spark, and Trino integrations), and transactions.
It's something that really sets Phoenix apart. It would be just a shame to let
that rot.
Yes, let's take it up on the dev list.
My priorities have since changed more into the bigger ecosystem of data (Trino,
Iceberg, Spark, Federation, Real-time Ingestion, M/L, Governance, etc). That
said, Phoenix has still a place in that ecosystem as I mentioned before, and so
I am still interested at that level.
> The Tephra transaction processor cannot be loaded anymore.
> ----------------------------------------------------------
>
> Key: PHOENIX-6615
> URL: https://issues.apache.org/jira/browse/PHOENIX-6615
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.1.2
> Reporter: Lars Hofhansl
> Priority: Major
> Attachments: 6615.txt
>
>
> See
> # TransactionFactory
> # TephraTransactionProvider
> Can you spot the problem? :) (Hint: The constructor is private.)
> Broken since PHOENIX-6064. [~stoty] .
> Can I just say... Unless I am missing something... How could we not have
> noticed that one of the transaction processors has not been working since
> August (in 5.x at least)? Is really nobody using the transaction engines?
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
