stack commented on HBASE-12894:
On Constants being local to REST, that is my mistake. I did not notice. Excuse
On jetty6 being in different package, yes, that makes us safe against old
jetty6 at least.
You bring up a good point on the jersey and servlet versions. I took a look
over at hadoop and currently our versions are aligned, even on the hadoop3
alpha. Spark is on the servlet and jersey version you move us to in this patch.
We could exclude which would work for the classpath we control. Any clash would
be in the server and rest modules only. We have a switch to disable webservice
so could avoid trying to load these classes in problematic contexts.
Hmm. Anyone else have an opinion here? [~busbey] or [~enis]? My inclination is
to commit this patch and then file a follow-on issue whose subject is "How to
deal with updated libraries in hbase2". My thought is that we will have bigger
issues than the two libs here.
> Upgrade Jetty to 9.2.6
> Key: HBASE-12894
> URL: https://issues.apache.org/jira/browse/HBASE-12894
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Affects Versions: 0.98.0
> Reporter: Rick Hallihan
> Assignee: Guang Yang
> Labels: MicrosoftSupport
> Fix For: 2.0.0
> Attachments: HBASE-12894_Jetty9_v0.patch, HBASE-12894_Jetty9_v1.patch
> The Jetty component that is used for the HBase Stargate REST endpoint is
> version 6.1.26 and is fairly outdated. We recently had a customer inquire
> about enabling cross-origin resource sharing (CORS) for the REST endpoint and
> found that this older version does not include the necessary filter or
> configuration options, highlighted at:
> The Jetty project has had significant updates through versions 7, 8 and 9,
> including a transition to be an Eclipse subproject, so updating to the latest
> version may be non-trivial. The last update to the Jetty component in
> https://issues.apache.org/jira/browse/HBASE-3377 was a minor version update
> and did not require significant work. This update will include a package
> namespace update so there will likely be a larger number of required changes.
This message was sent by Atlassian JIRA