-
Notifications
You must be signed in to change notification settings - Fork 152
Errors using consumer with ES 2.0 #8
Comments
Do we have a resolution for this? I am seeing the same failure for ES 2.x |
I was/am having the same issue and now I've gotten a little further, I'm not Java programmer so pardon my ignorance. But I've updated the
This caused a new issue during my Maven install:
I found out that the So I added this dependency to the pom.xml for
And I changed
After doing this, I can do a The new issue I've run into is this:
It looks like the I'm going to add some logic to differentiate between 1.x and 2.x and test locally, if it works, I'll make a PR back to amazon-kinesis-connectors with the fix. +@dvassallo for visibility, he's been great at helping me through this struggle :) |
OK, I just spent all day getting this to work, it is a two-part problem. The first part is that the amazon-kinesis-connectors library needs to be updated to support elasticsearch 2.0, I've created a PR based on my work today amazon-archives/amazon-kinesis-connectors#63. The second part is that the current cloudwatch-logs-subscription-consumer uses org.elasticsearch.common.lang which WAS a shade of org.apache.commons.lang in elasticsearch 1.x, now shades are gone and you call the classes directly. A new PR has been made here that has examples on how to make it work for 2.x #11. |
Hi - I'm attempting to use the consumer with our ES 2.0 cluster and am receiving errors. I know there were some breaking changes with the Java API in ES 2.0, so I'm assuming that is the issue here, but I'm hoping to give as much info as possible in order to get this resolved.
The consumer was compiled as instructed in the Readme with default configuration other than the ES cluster details and TRACE logging.
The error I am receiving on the consumer side is:
The error that I am receiving on the Elasticsearch side is:
Both the ES cluster and the consumer are using Java 1.7.0_91.
Please let me know if there is anything else I can add.
Thanks.
The text was updated successfully, but these errors were encountered: