-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.2.4 release broke plugin #9592
Comments
andrewvc
added a commit
to andrewvc/logstash
that referenced
this issue
May 21, 2018
We only depended on it transitively in the past, this makes it explicit. This caused an issue in the google pubsub plugins, reported here: elastic#9592 In the future, this will be a non-concern when your java plugin API launch with classloader isolation.
@josephlewis42 apologies. #9622 should fix this. The real fix is #9215 , which will include a parent last class loader policy that will let you bundle your own Guava. |
@andrewvc thank you so much! |
This was referenced May 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
It looks like this PR in the 6.2.4 Logstash release broke the
logstash-input-google_pubsub
plugin. More info about it is in this pubsub PR.Reverting the version of
google-java-format
from 1.5 to 1.1 caused the guava version to drop from 22 (released in 2017) to 19 (released in 2015).This issue is likely to come up with the four (soon to be five) other Google Logstash plugins to stop working as the Google Cloud API changes.
Is there any way to get the Guava version bumped back up to 20 or above? Or is there something we can do on our side to make sure our Guava JAR is used over the bundled one?
Thanks!
The text was updated successfully, but these errors were encountered: