[ 
https://issues.apache.org/jira/browse/SOLR-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456989#comment-16456989
 ] 

Varun Thacker commented on SOLR-10036:
--------------------------------------

Here's my analysis:
- We can't remove jackson. Calcite/hadoop and probably a few other projects 
needs it as a dependency. Currently within Solr a few contribs use jackson-core 
directly.
- Current Hadoop version: 2.7.4
- hadoop-common and hadoop-hdfs ( 2.7.4 ) explicitly have jackson 1.9.13 as a 
dependency
- Solr currently uses Jackson 2.5.4 and the latest Jackson version is 2.9.5
- Didn't run into any issues while running "ant test" and "ant 
-Dtests.nightly=true "-Dtests.class=org.apache.solr.cloud.hdfs.*"" ( one test 
was hung but that's probably the test being flaky. Didn't have any class not 
found issues )

 

[~elyograg] I think we should just commit this? 

> 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: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Shashank Pedamallu
>            Assignee: Varun Thacker
>            Priority: Major
>         Attachments: SOLR-10036.patch
>
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to