Conversation
|
Didn't dig into the code, but from looking at the errors it looks like you might need to add a maven munge directive here - seems there might by a method being called that's not valid for accumulo 1.5 |
|
I didn't see it that way, at least in the last failure what I saw was it failing on a random zookeeper transaction related test unrelated to this example code. I think there's at least two random failures in our tests, I ticketed one #361 and I probably should have added an issue for this before restarting. We'll probably see it again. |
or where accumulo is org.apache.accumulo.minicluster.MiniAccumuloCluster the getConnector method is marked as "since 1.6.0" . I think I win! :) |
|
We test against 1.5.2 in travis. :) https://github.com/ngageoint/geowave/blob/master/.travis.yml#L7 Coincedentally, your test is only failing in 1.5.2 on travis. https://travis-ci.org/ngageoint/geowave/builds/61651413 Munge it up, brother! EDIT: Dogpile!!! On Fri, May 8, 2015 at 4:18 PM, Chris Bennight notifications@github.com
|
|
To be fair, could possibly skip munge and just go with a 1.5 compatible method if it isn't deprecated. Hopefully when 1.7 get's out we can cut some of the 1.5 support. |
|
@chrisbennight you win this time ;) I don't know what I was looking at with the transaction stuff - I'll just stick to the claim that the one test I had restarted happened to have the random issue before it got to compiling the examples. |
|
Sorry for the oversight - should be fixed now. I took @chrisbennight recommended approach and simply avoided the use of a 1.6-only method. |
GeoTools query example for #116