Thanks for the clarification Siyuan.
On Sun, Apr 17, 2016 at 3:34 PM, hsy...@gmail.com wrote:
> Hey Ananth,
>
> We have semantic version control. For public library/Api, they should stay
> no change in major release, so most operator in 3.3.x should be able to
> work with 3.3.0 engine. The only
Hey Ananth,
We have semantic version control. For public library/Api, they should stay
no change in major release, so most operator in 3.3.x should be able to
work with 3.3.0 engine. The only exception is Api that marked
@evolving(nonstable). Kafka 0.9 is one of them. But I don't see any feature
o
Hello Siyuan/Ram,
Thanks for the inputs.
I was able to resolve the problem by excluding the dependencies of
malhar-library and malhar-contrib from the dependency sections of the
apex-engine , apex-api .
This made the 3.3.1-incubating version of the malhar kick into the
classpath and subsequently
Hi Ananth,
Could you please try to add malhar-library in test scope? Thanks!
Regards,
Siyuan
On Saturday, April 16, 2016, Ananth Gundabattula
wrote:
> Hello all,
>
> I would like to run a unit test code using the new Kafka Operator that
> supports the 0.9 version protocol.
>
> In this process,
Ananth,
Could you make your pom.xml accessible somewhere ?
Ram
On Sat, Apr 16, 2016 at 3:30 PM, Ananth Gundabattula <
agundabatt...@gmail.com> wrote:
> Hello all,
>
> I would like to run a unit test code using the new Kafka Operator that
> supports the 0.9 version protocol.
>
> In this process,
Hello all,
I would like to run a unit test code using the new Kafka Operator that
supports the 0.9 version protocol.
In this process, I included the malhar-kafka library version (
3.3.1-incubating ) and am using the apex-engine ( version 3.3.0 ) with
as test/provided.
The compilation works fine