That build breakage is caused by the Omid change to use the new module, not the new module itself. So that's an argument for bumping the Omid version, not the thirdparty version.
Istvan On Mon, Oct 13, 2025 at 12:18 PM Mészáros Norbert <[email protected]> wrote: > Hi, > > In Phoenix the usage of the new version of Omid with the Phoenix Thirdparty > change results in a build failure for which a fix is ready PHOENIX-7714. > Since it breaks the Phoenix build I'd think the 3.0.0 version should be > more appropriate. > > Kind regards, > Norbert Mészáros > > Istvan Toth <[email protected]> ezt írta (időpont: 2025. okt. 13., H, > 10:14): > > > Hi, > > > > One open security issue is the use of protobuf 2.5.0 by Omid. > > As discussed in a recent thread > > https://lists.apache.org/thread/rthnk6vxx5y6cr7t5kkkx2vj9c91nf37 > > using unshaded protobuf in a library is no longer viable because of > > protobuf 3/4 api incompatibilities, hence we need to use a shaded > protobuf > > artifact for OMID. > > > > I propose releasing a new phoenix-thirdparty release which includes it > own > > shaded protobuf library (similarly to HBase, but without the patches) > > > > At the moment the version is 2.2.0, bumped from 2.1.x, but we could also > go > > to 3.0.0, I'm not sure which one is better. > > > > Please share your thoughts. > > > > Istvan > > > -- *István Tóth* | Sr. Staff Software Engineer *Email*: [email protected] 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> ------------------------------ ------------------------------
