Re: asm IllegalArgumentException with 1.0.0

2016-04-20 Thread David Kim
Hi Stephan! Following up on this issue, it seems the issue doesn't show itself when using version 1.0.1. I'm able to run our unit tests in IntelliJ now. Thanks! David On Wed, Apr 13, 2016 at 1:59 PM Stephan Ewen wrote: > Does this problem persist? (It might have been caused by maven caches wit

Re: asm IllegalArgumentException with 1.0.0

2016-04-13 Thread Stephan Ewen
Does this problem persist? (It might have been caused by maven caches with bad artifacts). The many transitive dependencies you see often come from the connectors - that is also why we do not put the connectors into the lib folder directly, so that these libraries are not always part of every Flin

Re: asm IllegalArgumentException with 1.0.0

2016-03-14 Thread Zach Cox
Yes pretty much - we use sbt to run the job in a local environment, not Intellij, but should be the same thing. We were also seeing that exception running unit tests locally. We did not see the exception when assembling a fat jar and submitting to a remote Flink cluster. It seems like the flink-co

Re: asm IllegalArgumentException with 1.0.0

2016-03-14 Thread Andrew Whitaker
We're having the same issue (we also have a dependency on flink-connector-elasticsearch). It's only happening to us in IntelliJ though. Is this the case for you as well? On Thu, Mar 10, 2016 at 3:20 PM, Zach Cox wrote: > After some poking around I noticed > that flink-connector-elasticsearch_2.1

Re: asm IllegalArgumentException with 1.0.0

2016-03-10 Thread Zach Cox
After some poking around I noticed that flink-connector-elasticsearch_2.10-1.0.0.jar contains shaded asm classes. If I remove that dependency from my project then I do not get the IllegalArgumentException. On Thu, Mar 10, 2016 at 11:51 AM Zach Cox wrote: > Here are the jars on the classpath whe

Re: asm IllegalArgumentException with 1.0.0

2016-03-10 Thread Zach Cox
Here are the jars on the classpath when I try to run our Flink job in a local environment (via `sbt run`): https://gist.githubusercontent.com/zcox/0992aba1c517b51dc879/raw/7136ec034c2beef04bd65de9f125ce3796db511f/gistfile1.txt There are many transitive dependencies pulled in from internal library

Re: asm IllegalArgumentException with 1.0.0

2016-03-10 Thread Stephan Ewen
Dependency shading changed a bit between RC4 and RC5 - maybe a different minor ASM version is now included in the "test" scope. Can you share the dependencies of the problematic project? On Thu, Mar 10, 2016 at 12:26 AM, Zach Cox wrote: > I also noticed when I try to run this application in a l

Re: asm IllegalArgumentException with 1.0.0

2016-03-09 Thread Zach Cox
I also noticed when I try to run this application in a local environment, I get the same IllegalArgumentException. When I assemble this application into a fat jar and run it on a Flink cluster using the CLI tools, it seems to run fine. Maybe my local classpath is missing something that is provide