Yes, the proposal was not to bundle the Omid coprocessors into the Phoenix
server Jar.

However, I could not find an attractive solution to achieve this.

On Thu, Dec 7, 2023 at 7:30 PM Geoffrey Jacoby <gjac...@apache.org> wrote:

> Cong,
>
> Tephra support has already been removed from Phoenix 5.2. See
> https://issues.apache.org/jira/browse/PHOENIX-6627.
>
> It had a number of dependencies that were out of date and no longer being
> maintained with known CVEs, and didn't seem to have many (if any) users
> relying on it.
>
> Geoffrey
>
> On Wed, Dec 6, 2023 at 6:51 PM Cong Luo <l...@apache.org> wrote:
>
> > And then
> > Is it possible to remove tephra component(eg. Processor, Context,
> > Provider...) from the phoenix codebase starting with 5.2? Because omid is
> > production ready earlier than tephra, and tephra maintenance is
> > diminishing, we may no longer need the tephra.
> >
> > On 2023/12/06 09:13:30 Istvan Toth wrote:
> > > Hi!
> > >
> > > We are currently including the Omid coprocessors in Phoenix-server.
> > >
> > > I think that this is problematic.
> > >
> > > In order to use Omid, users have to install and configure the TSO
> server
> > on
> > > the cluster.
> > >
> > > The Omid install instructions (correctly) include the steps to install
> > the
> > > Omid coprocessors to HBase.
> > >
> > > So if the user follows all instructions, then they are going to end up
> > with
> > > two instances of the coprocessors in the HBase classpath.
> > >
> > > I propose removing the coprocessors from phoenix-server on master (not
> on
> > > 5.1).
> > >
> > > What do you think ?
> > >
> > > Istvan
> > >
> >
>


-- 
*István Tóth* | Sr. Staff Software Engineer
*Email*: st...@cloudera.com
cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
------------------------------
------------------------------

Reply via email to