Niclas Hedhman a écrit :
Bringing this up again, since it seems to be an issue in the Elastic Search
extension...
I have found the answer to the problem as well, explained on
http://elasticsearch-users.115913.n3.nabble.com/Testing-the-index-existence-td4019208.html
i.e. The exists API isn't
[
https://issues.apache.org/jira/browse/ZEST-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587647#comment-14587647
]
Jiri Jetmar commented on ZEST-31:
-
Evtl. this has to do with the @Aggregated settings ? I;m
Niclas Hedhman a écrit :
Board doesn't really have an opinion on the matter. It would be trademarks@
or maybe infra.
I am sure we can make it stick to 'org.qi4j' IF we also declare that 3.0 is
next and it is converging there.
Apache River is still using net.jini package names and such, and
[
https://issues.apache.org/jira/browse/ZEST-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587756#comment-14587756
]
Niclas Hedhman commented on ZEST-31:
Ok, but traversal won't work as the Module of the