The shaded omid-hbase-coprocessor-1.1.1-SNAPSHOT.jar includes parts of Omid that the coprocessors depend on.
We could shade the omid classes inside phoenix-server, that way they wouldn't interfere, but IIRC that would break Yaml parsing. So there doesn't seem to be a clear path forward with this. On Wed, Dec 6, 2023 at 10:44 AM Istvan Toth <st...@apache.org> wrote: > We'd have to figure out how those interact with the (unshaded) Omid > libraries in Phoenix-server. > > On Wed, Dec 6, 2023 at 10:13 AM Istvan Toth <st...@apache.org> 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 >> >>
