[
https://issues.apache.org/jira/browse/HADOOP-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150766#comment-14150766
]
Steve Loughran commented on HADOOP-10104:
-----------------------------------------
Are these with things being served up over HTTP? With Jersey? because
https://java.net/jira/browse/JERSEY-989 shows that it has "issues" with
{{@JsonProperty}} annotations, where issues==appears to ignore them (seen in
YARN-913 rest API; surfaces in SLIDER-454.
Though looking at the HBASE JIRA, it's more than "jackson 1.8.13 actually
listens to the JAXB annotations", hence served things up with the declared
properties, rather than field names" —fixing the marshalling problems I'd seen.
w.r.t classpath solutions, OSGi is the only one we could seriously push people
downstream at as an option, and run in-house. Even without the Hadoop processes
themselves running in OSGi containers, the hadoop JARs could all be OSGi
enabled.
> Update jackson to 1.9.13
> ------------------------
>
> Key: HADOOP-10104
> URL: https://issues.apache.org/jira/browse/HADOOP-10104
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build
> Affects Versions: 2.2.0, 2.3.0, 2.4.0
> Reporter: Steve Loughran
> Assignee: Akira AJISAKA
> Priority: Minor
> Fix For: 2.5.0
>
> Attachments: HADOOP-10104-003.patch, HADOOP-10104.2.patch,
> HADOOP-10104.4.patch, HADOOP-10104.patch
>
>
> Jackson is now at 1.9.13,
> [apparently|http://mvnrepository.com/artifact/org.codehaus.jackson/jackson-core-asl],
> hadoop 2.2 at 1.8.8.
> jackson isn't used that much in the code so risk from an update *should* be
> low
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
