Elasticsearch Documentation and Implementation Differences

[alexiudice]

While learning to use the apoc Elasticsearch integration I found some head-scratching problems. There are discrepancies between the apoc Elasticsearch methods and the apoc Elasticsearch documentation.

1. The documentation and implementation for 'apoc.es.post' differ on the id parameter. The documentation has no id parameter, but the function REQUIRES an id parameter when being used. This seems to be a mistake, as it makes the apoc.es.post and apoc.es.put implementations identical. From the documentation it seems they should be different and apoc.es.post is not supposed to include an id, since elasticsearch can automatically generate it.

2. Documentation on both apoc.es.post and apoc.es.put are wrong on the last parameter. The documentation says the last param can be payload-or-null. The payload cannot be ‘null’, or Neo4j (tested on Neo4j version 3.2.9) throws the following exception:

Failed to invoke procedure 'apoc.es.post': Caused by: java.lang.RuntimeException: Can't read url http://localhost:9200/test-index/doc/1 as json: cannot write to a URLConnection if doOutput=false - call setDoOutput(true).

The parameter also cannot be missing, as no default is set. The only acceptable parameter is some sort of map.