Glad to hear it’s working!
Yes, normally you should avoid using the lib folder to resolve these dependency
issues and rely only on user jar packaging when working with Flink connectors.
- Gordon
On 17 July 2017 at 9:44:20 PM, Fabian Wollert (fabian.woll...@zalando.de) wrote:
TL;DR: remove
TL;DR: remove all lucene and elasticsearch libs in your flink env and just
use maven to manage dependencies, when working with the flink elasticsearch
connector.
so in the first place i deleted the libs in the folder to see if its
working, but it did not. then we thought if maybe flink loads
Hi,
I would also recommend checking the `lib/` folder of your Flink installation to
see if there is any dangling old version jars that you added there.
I did a quick dependency check on the Elasticsearch 2 connector, it is
correctly pulling in Lucene 5.5.0 only, so this dependency should not
1.3.0, but i only need the ES 2.X connector working right now, since that's
the elasticsearch version we're using. another option would be to upgrade
to ES 5 (at elast on dev) to see if its working as well, but that sounds
not like fixing the problem for me :-D
Cheers
Fabian
--
*Fabian
Hi,
There was also a problem in releasing the ES 5 connector with Flink 1.3.0. You
only said you’re using Flink 1.3, would that be 1.3.0 or 1.3.1?
Best,
Aljoscha
> On 16. Jul 2017, at 13:42, Fabian Wollert wrote:
>
> Hi Aljoscha,
>
> we are running Flink in Stand
Hi Aljoscha,
we are running Flink in Stand alone mode, inside Docker in AWS. I will
check tomorrow the dependencies, although i'm wondering: I'm running Flink
1.3 averywhere and the appropiate ES connector which was only released with
1.3, so it's weird where this dependency mix up comes from ...
This kind of error almost always hints at a dependency clash, i.e. there is
some version of this code in the class path that clashed with the version that
the Flink program uses. That’s why it works in local mode, where there are
probably not many other dependencies and not in cluster mode.
Hi Timo, Hi Gordon,
thx for the reply! I checked the connection from both clusters to each
other, and i can telnet to the 9300 port of flink, so i think the
connection is not an issue here.
We are currently using in our live env a custom elasticsearch connector,
which used some extra lib's
Hi Fabian,
I loop in Gordon. Maybe he knows whats happening here.
Regards,
Timo
Am 13.07.17 um 13:26 schrieb Fabian Wollert:
Hi everyone,
I'm trying to make use of the new Elasticsearch Connector