[
https://issues.apache.org/jira/browse/SOLR-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840774#comment-15840774
]
Mike Drob commented on SOLR-10036:
----------------------------------
+1 to upgrade versions - Jackson has been much better about documenting their
back compat issues recently than they were in the days of 1.x
Looking over the list, there shouldn't be anything that affects us. Hadoop
stopping at 2.7.x is surprising to me, but it looks like they are planning on
jackson 2.8.x in hadoop 3 (which will happen may or may not happen in our
lifetimes).
While I'd generally suggest using the last patch release of the minimum
supported version we need to get things working (2.6.7) for client compat
reasons, the security fixes in only present in 2.7.x+ push me towards that
instead.
tl;dr: I trust Jackson to be largely compatible across the board, and where
possible we should not hold ourselves to Hadoop's "latest and greatest of 2005"
philosophy.
> Revise jackson-core version from 2.5.4 to latest
> ------------------------------------------------
>
> Key: SOLR-10036
> URL: https://issues.apache.org/jira/browse/SOLR-10036
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Shashank Pedamallu
> Priority: Blocker
>
> The current jackson-core dependency in Solr is not compatible with Amazon AWS
> S3 dependency. AWS S3 requires jackson-core-2.6.6 while Solr uses
> jackson-core-dependency-2.5.4. This is blocking the usage of latest updates
> from S3.
> It would be greatly helpful if someone could revise the jackson-core jar in
> Solr to the latest version. This is a ShowStopper for our Public company.
> Details of my Setup:
> Solr Version: 6.3
> AWS SDK version: 1.11.76
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
