[
https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133774#comment-16133774
]
stack commented on HBASE-18615:
-------------------------------
Ok. This took a while. Now I can run REST in all three locations -- standalone
out of a tarball, in-place inside a build dir after build, and unit tests pass.
The patch is for branch-2 for now. The master and branch-2 have deviated a
little around jersey/jackson handling.
This article was of help:
https://stackoverflow.com/questions/39458230/how-register-jacksonfeature-on-clientconfig
It explained what the Jackson1Feature setting in RESTServer was supposed to do.
Explained it dodgy and the proper alternative.
It took me a while to then figure that the TestRESTServer class was different
in branch-2 to master.
I filtered out all of hadoops jersey1s. This helped for the case where we are
running in-situ -- no jersey1 pollution.
It seems like java will default to jersey1 if nothing else found so cut-it off
by setting a jersey2 RuntimeDelegate as soon as the RESTServer starts.
Remove all jackson1 references and includes of jersey-media-json-jackson1.
Lets see how this patch does now.
> hbase-rest tests fail in hbase-2.0.0-alpha2
> -------------------------------------------
>
> Key: HBASE-18615
> URL: https://issues.apache.org/jira/browse/HBASE-18615
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt
>
>
> Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
