You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2018/06/09 12:06:00 UTC
[jira] [Closed] (STORM-2884) Storm-druid topologies fail with
NoSuchMethodError (Storm 2.0)
[ https://issues.apache.org/jira/browse/STORM-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim closed STORM-2884.
-------------------------------
Resolution: Won't Fix
We decided to remove storm-druid in 2.0.
> Storm-druid topologies fail with NoSuchMethodError (Storm 2.0)
> --------------------------------------------------------------
>
> Key: STORM-2884
> URL: https://issues.apache.org/jira/browse/STORM-2884
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Arun Mahadevan
> Assignee: Arun Mahadevan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Deploy a sample topology with storm-druid (E.g. the SampleDruidBoltTopology available in the storm git repo). The worker crashes with below error:
> {noformat}
> 2017-12-28 15:47:36.382 o.a.s.util Thread-11-113-Violation-Events-Cube-executor9 9 ERROR Async loop died!
> java.lang.NoSuchMethodError: org.apache.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lorg/apache/curator/framework/api/ProtectACLCreateModePathAndBytesable;
> at com.metamx.tranquility.beam.ClusteredBeam$$anonfun$com$metamx$tranquility$beam$ClusteredBeam$$zpathWithDefault$1.apply(ClusteredBeam.scala:125) ~dep-org.apache.storm-storm-druid-jar-1.2.0.3.1.0.0-420.jar.1514384427000:1.2.0.3.1.0.0-420
> at com.metamx.tranquility.beam.ClusteredBeam$$anonfun$com$metamx$tranquility$beam$ClusteredBeam$$zpathWithDefault$1.apply(ClusteredBeam.scala:122) ~dep-org.apache.storm-storm-druid-jar-1.2.0.3.1.0.0-420.jar.1514384427000:1.2.0.3.1.0.0-420
> at com.metamx.common.scala.Predef$EffectOps.withEffect(Predef.scala:44) ~dep-org.apache.storm-storm-druid-jar-1.2.0.3.1.0.0-420.jar.1514384427000:1.2.0.3.1.0.0-420
> at
> {noformat}
> storm-druid has dependency on curator 2.6.0, but the storm parent pom has defined 4.0.0 version in the dependency Management.
> Due to this storm-druid is inheriting the 4.0.0 version of curator and including that version in the jar.
> If we explicitly mention the curator dependency in the storm-druid pom.xml, this can be addressed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)