[
https://issues.apache.org/jira/browse/STORM-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329229#comment-15329229
]
ASF GitHub Bot commented on STORM-1881:
---------------------------------------
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1480
We're shading the libraries which you're changing scope to `provided` in
storm-core, so it will not be provided at runtime.
Since storm-redis depends on Guava, placing uber storm-redis jar to extlib
incurs dependency issue in whole topologies in cluster. If we still really want
to place this to extlib, we may need to consider shading guava and others for
storm-redis module.
> storm-redis is missing dependant libraries in distribution
> ----------------------------------------------------------
>
> Key: STORM-1881
> URL: https://issues.apache.org/jira/browse/STORM-1881
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-redis
> Affects Versions: 1.0.1
> Reporter: Daniel Klessing
>
> Despite the documentation on
> http://storm.apache.org/releases/1.0.1/State-checkpointing.html it is not
> enough to simply copy {{storm-redis-*.jar}} to {{extlib}} to get the
> {{RedisKeyValueStateProvider}} working. Depending jedis and
> apache-commons-pool2 jars are missing and must be copied by hand to get it
> working. Else one is greeted with exception stack traces like:
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.pool2.impl.GenericObjectPoolConfig
> {code}
> or
> {code}
> Caused by: java.lang.ClassNotFoundException:
> redis.clients.jedis.JedisPoolConfig
> {code}
> Copying {{commons-pool2-2.4.2.jar}} and {{jedis-2.8.1.jar}} from hand to
> {{extlib}} solves the issue.
> It might be better to create a "fat" jar of {{storm-redis-*.jar}} or provide
> documentation, which libraries have to be made available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
