[ 
https://issues.apache.org/jira/browse/STORM-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Veil updated STORM-530:
---------------------------
    Description: 
Storm 0.9.2 seems to ship with version 4.1.1 of HttpClient in its lib 
directory.  This version is very out dated (GA in May of 2011) and becomes 
problematic when integrating tools like Solr with Storm.   Solr 4.7.2 for 
example depends on a much newer version 4.3.1 (GA in October 2013).  This may 
be resolved by STORM-447, but wanted to make sure this was part of that fix.

The workaround seems to be replacing the older versions in the lib directory 
with newer ones, but that shouldn't be required for such a simple integration.

  was:
Storm 0.9.2 seems to ship with version 4.1.1 of HttpClient in its lib 
directory.  This version is very out dated (GA in May of 2011) and becomes 
problematic when integrating tools like Solr with Storm.   Solr 4.7.2 for 
example depends on a much newer version 4.3.1 (GA in October 2013).  This may 
be resolved by STORM-447, but wanted to make sure this was part of that fix.

The workaround seems to be replacing the older versions in the lib directory 
with newer ones, but that shouldn't be a required.


> Upgrade version of HttpClient
> -----------------------------
>
>                 Key: STORM-530
>                 URL: https://issues.apache.org/jira/browse/STORM-530
>             Project: Apache Storm
>          Issue Type: Dependency upgrade
>    Affects Versions: 0.9.2-incubating
>            Reporter: Tim Veil
>
> Storm 0.9.2 seems to ship with version 4.1.1 of HttpClient in its lib 
> directory.  This version is very out dated (GA in May of 2011) and becomes 
> problematic when integrating tools like Solr with Storm.   Solr 4.7.2 for 
> example depends on a much newer version 4.3.1 (GA in October 2013).  This may 
> be resolved by STORM-447, but wanted to make sure this was part of that fix.
> The workaround seems to be replacing the older versions in the lib directory 
> with newer ones, but that shouldn't be required for such a simple integration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to