[
https://issues.apache.org/jira/browse/PHOENIX-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6861:
---------------------------------
Release Note: Due to an incompatible change in the way phoenix-client is
shaded and relocated, when using PQS with Phoenix 5.1.0 - 5.1.3 or 4.16.x, PQS
must be built with the "shade-javax-servlet" maven profile enabled.
> PQS fails to start because of relocated javax.servlet with Phoenix 5.2
> ----------------------------------------------------------------------
>
> Key: PHOENIX-6861
> URL: https://issues.apache.org/jira/browse/PHOENIX-6861
> Project: Phoenix
> Issue Type: Bug
> Components: queryserver
> Affects Versions: queryserver-6.0.1
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> We've made to relatively recent changes to javax.servelt in the shaded PQS
> client JAR.
> In PHOENIX-6151 we've applied shading to it, then in PHOENIX-6703 we've
> removed it altogether from the embedded client JAR.
> Also relatively recently, we have added a dependency for
> org.apache.hadoop.jmx.JMXJsonServlet to PQS.
> As a result, we have mutually incompatible requirements for the PQS classpath.
> For old phoenix-client versions, and for current 5.2 phoenix-client versions
> with PHOENIX-6703, we need to have unshaded javax.servlet, both for Avatica,
> and for JMXJsonServlet on the classpath.
> On the other hand, for Phoenix versions that have PHOENIX-6151, but not
> PHOENIX-6703, we need to shade javax.servlet so that it matches with shading
> applied for JMXJsonServlet (which is coming via phoenix-client, which shades
> javax.servlet).
> We need to find some kind of solution to this mess, ideally so that the same
> PQS binary works with as many Phoenix versions as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
