[
https://issues.apache.org/jira/browse/PHOENIX-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463052#comment-17463052
]
Istvan Toth commented on PHOENIX-6615:
--------------------------------------
On transaction support generally:
Yes, I do get the feeling that very few people are using it, and if they do,
they are not telling.
Even before I broke it in PHOENIX-6064 Tephra support has been broken more than
not, as Tephra needs a new release for every HBase minor version, otherwise it
will fail to start. The last release supports up to HBase 2.4 and 1.6 IIRC.
(The IT suite doesn't catch the missing HBase support, either)
The glass is actually half-full, as we do support Omid + Phoenix at dayjob, and
if you check the commit log, Rajeshbabu and I ironed out quite a few kinks out
of that in the past year (like Kerberos not working at all), so we know that
Omid and Phoenix + Omid is in a workable state (at least on our branch, which
is basically Omid HEAD, minus the incompatible maven changes).
We are also regularly running some (basic) E2E tests for it.
(Omid needs a new release to get the rest of those fixes and improvements
officially out, BTW)
We did have two Omid contributors, who are not on the #dayjob team in the last
year, with some much needed Omid build system improvements, but not even any
bug reports on Tephra.
We have worked on Tephra, mostly to keep Tephra working with newer HBase minore
releases, and to somewhat isolate us from the CVEs in it, but more out of
wanting the keep Phoenix CVE free (check) and intact (fail), than because we
had any plans for Tephra beyond that.
In other words, the work we do on Tephra relates more to keeping the rest of
Phoenix building and safe than keeping Tephra working (much less improving it).
All that I know about Tephra and Tephra support in Phoenix points to it being
abandoned at this point.
As any unmaintained code, Tephra is a liability, (hence PHOENIX-6064), and
making Tephra secure is a non-trivial amount of work. (need to rip out and
replace Twill, and update Guava at least, and fix any JVM incompatibilities
that you've mentioned) I estimate that it'd take about 1-3 weeks depending on
familiarity with Twill, Guava and ZK.
I'm of course going to test and apply your fix to PHOENIX-6064 (thanks again),
and I may make Tephra point releases for new HBase minor versions (1.7 support
is known to be missing), but if no maintainer steps up for Tephra (who actually
cares about it, and can commit time to it), then we need to revisit the
previous discussion on the long-term viability of Tephra.
I'm beginning to doubt that the half-hearted job I do at maintaining Tephra
(i.e. adding support for new HBase releases) is beneficial, as it may give the
illusion of a properly maintained project to an outside observer.
Should we take the Tephra discussion to the dev/user list next year ?
> 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)
