Open ishare opened 9 years ago
The original spatial library is an external library that relied on the older IndexProvider API to act like a legacy index. The newer schema indexes are much harder to integrate with as an external library. So we are planning an all-new version of spatial that will be integrated into Cypher and include and index that acts much more similarly to the schema indexes. This work is on-going, but has no currently known release date, so I cannot comment on that.
Also, the /schema/index REST API is not necessarily going to be supported. The priority is to support schema indexes for spatial inside Cypher, with the REST API being something that has lower priority. Do you specifically need REST support for this? You will be able to create and delete these indexes from cypher, so I guess that will be sufficient?
It seems REST API is much more efficient than Cypher, I doubt why you choose to support Cypher first? And may I ask you, how can I get the distance between the target location, using cypher? Thanks
I found you use legacy index in the doc, and the cypher query is not working. http://neo4j-contrib.github.io/spatial/#rest-api-create-a-spatial-index
How can I use latest index method '/schema/index', instead of '/index/node'? And is there a good way to support query filter by other properties? Thanks.