Hello Bright,
Did the maven approach of excluding guava dependencies when specifying malhar
not work ?
By this I mean using the following stub when adding malhar dependency in your
Pom.xml?
<exclusions>
<exclusion>
<groupId>com.google.guava</groupId> <artifactId>guava</artifactId>
</exclusion>
</exclusions>
Regards
Ananth
> On 2 Dec. 2016, at 1:02 pm, Munagala Ramanath <[email protected]> wrote:
>
> Bright,
>
> We have this in contrib/pom.xml which I think is causing the problem:
>
> <dependency>
> <groupId>com.google.guava</groupId>
> <artifactId>guava</artifactId>
> <version>16.0.1</version>
> <scope>provided</scope>
> <optional>true</optional>
> </dependency>
>
> whereas the hadoop-common 2.2.0 depends on 11.0.2
>
> Ram
>
>> On Thu, Dec 1, 2016 at 4:11 PM, Bright Chen <[email protected]> wrote:
>>
>> Hi All,
>> I got an runtime exception (In unit test in local mode) when trying to test
>> Guava BloomFilter in malhar. the exception is as following. It seem the
>> malhar depended on Guava 11.0.2 at compile time while depended on higher
>> version at runtime. Which caused this compatible issue.
>>
>> Anyone got same issue or any idea how to solve or get around this issue?
>>
>> java.lang.AbstractMethodError:
>> org.apache.apex.malhar.lib.state.managed.SliceFunnel.
>> funnel(Ljava/lang/Object;Lcom/google/common/hash/PrimitiveSink;)V
>>
>> at
>> com.google.common.hash.AbstractStreamingHashFunction$
>> AbstractStreamingHasher.putObject(
>> AbstractStreamingHashFunction.java:223)
>>
>> at com.google.common.hash.AbstractStreamingHashFunction.hashObject(
>> AbstractStreamingHashFunction.java:37)
>>
>> thanks
>> Bright
>>
