[PHOENIX-6144] Phoenix client coexistence with other hadoop components in the same JVM

• Type: Wish
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: core
• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 18/Sep/20 07:57
• Updated: 29/Jul/21 12:15
• Resolved: 29/Jul/21 12:15

Description

We would like to offer a solution to use phoenix client concurrently with other hadoop components in the same VM. 

phoenix-client is not working in this case, because the components with relocations in the fat jar clash with the "normal" hadoop components.

Using the unshaded phoenix-core directly would be a possible solution, but this can easily result in version conflicts (in our specific case, protobuf 2.5 vs 3.x)

I could see two ways we could take: 

One is shading everything in phoenix-client outside org.apache.phoenix, so that there are guaranteed to be no conflicts. I doubt that this is actually feasible, but would love to be proven wrong.

Another solution would be expanding the existing thirdparty components. We could check what HBase does, and make a phoenix-thirdparty version that we also use.

I thought about using the components shaded into phoenix-client directly, but I think that we consider those an implementation detail, and don't want to commit to maintiaining compatibility, not to mention that they may have unexpected (to the user) relocations.

The current workaround is using PQS+thin client, but this not always optimal.

Issue Links

• depends upon: PHOENIX-6193 PHOENIX-6151 slows down shading
• depends upon: PHOENIX-6151 Switch phoenix-client to shade-by-default mode
• depends upon: PHOENIX-6176 Set zookeeper as provided in phoenix-server
• duplicates: PHOENIX-6053 Split Server Side Code into a Separate Module
• is related to: PHOENIX-6053 Split Server Side Code into a Separate Module
• links to: PR #910