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
Broken tests #27
Comments
The tests assume you have an Elasticsearch cluster running at localhost:9200 before running the tests. If you didn't have one running, that could be part of the problem. |
Hi @ash211, Haven't mentioned it above but I did run the tests with ES running at localhost:9200 but they fail. Are they passing OK for you? (mind the 'clean' task in the gradlew call). Checking CascadingHadoopTest and CascadingLocalTest reviles an incorrect assumption that the testWriteToES() method is called before the testReadFromES(). JUnit does not guaranty the order of execution. I will do some more digging. |
I observed the same thing -- even with an ES instance running some tests On Thu, Apr 11, 2013 at 7:27 AM, Christian Tzolov
|
Guys, thanks for reporting this - I'm on it and hope to fix it shortly. I'm currently working on adding the project into a CI server so the project health can be monitored effectively by everyone. I'll keep you posted. |
…ElasticSerach in before/after class
@costin, i've added a pull request (with couple of commits) that adds embedded es and resolves the tests and related code: https://github.com/elasticsearch/elasticsearch-hadoop/pull/31/commits |
Fixed in master (see additional comments from #32 ) |
To reproduce:
clone the es-hadoop/master repository and run:
Both the CascadingHadoopTest and the CascadingLocalTest faile.
Am I doing something wrong or missing some configuration?
The text was updated successfully, but these errors were encountered: