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
repository-hdfs does not work with elasticsearch 2.0.0-beta1 #545
Comments
There seems to be a difference between the ES behaviour in ZIP vs JAR mode. This is what I get when running the test suite (from the project):
The first exception has an issue associated with it here. The second is jar hell which acts as a warning not a fatal exception - ES keeps on running. That's not to say it shouldn't be removed rather that it doesn't seem fatal. Considering beta2 should be released soon, I'd rather test against that especially since Guava was/is removed. |
This is expected. Tests relax the Security Manager by only WARNING the user because you could hit some issues when running from the IDE. The pb here is that the JarHell stops at the very first conflict instead of printing all conflicts at once. @rmuir Do you think we could print all JarHell errors in one go? |
no we shouldn't. It will make things too complicated (think thousands of conflicting class files just from one jar or so). Then there would be a problem that its too noisy and so on. This code should stay simple... JarHell can be mean as hell: its the opposite of user-friendly :) |
This has been address in master (the upcoming v2.2.0-m2). It does however require the security manager to be disabled for the time being. |
me to got same issue. but i am using please help me some one |
When starting elasticsearch
2.0.0-beta1
with repository-hdfs2.2.0-m1
, I get:The text was updated successfully, but these errors were encountered: