ArangoDB version : 3.1.19 I believe there is still no way to define which geo index is used with AQL functions NEAR, WITHIN AND WITHIN_RECTANGLE.
It's still possible to define which geo index is used when querying over REST. *May that feature isn't documented yet ?* We must read the source code of the implementation of the AQL function NEAR <https://docs.arangodb.com/3.1/AQL/Functions/Geo.html#near> to find a response. We can check the source code of the implementation of the REST near method <https://docs.arangodb.com/3.1/HTTP/Indexes/Geo.html#returns-documents-near-a-coordinate> to check if the deprecated collection.near <https://docs.arangodb.com/3.1/Manual/Appendix/Deprecated/SimpleQueriesGeoQueries.html#near> method is used or not. Le dimanche 21 avril 2013 06:33:05 UTC+2, F21 a écrit : > > When querying over REST using near or within, the user can define which > geo index is used (if there are multiple indexes): > http://www.arangodb.org/manuals/1.3.devel/IndexGeoHttp.html#IndexGeoHttpNear > > In AQL, there appears to be no way to choose the index: > > NEAR(collection, latitude, longitude, limit, distancename) > > WITHIN(collection, latitude, longitude, radius, distancename) > > In this case, which index will be used? In other words, how does ArangoDb > choose which index to use? If we do not provide an index to > /_api/simple/near or /_api/simple/within, will the index used be the same > as the one automatically chosen when using AQL's NEAR() and WITHIN()? > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
