You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This puts the responsibility on the user to figure out the most efficient query plan, which is very hard as it depends on many factors such as the indexed data, the cost of computing distances vs. the bbox, the selectivity of the query, the selectivity of the other required parts of the query etc. We should remove it from the API and try to figure out query plans internally.
In terms of backward compatibility, I think we can only work on 5.x by removing it from the Java API completely and making it deprecated on the REST layer (the parser would simply ignore it).
This puts the responsibility on the user to figure out the most efficient query plan, which is very hard as it depends on many factors such as the indexed data, the cost of computing distances vs. the bbox, the selectivity of the query, the selectivity of the other required parts of the query etc. We should remove it from the API and try to figure out query plans internally.
In terms of backward compatibility, I think we can only work on 5.x by removing it from the Java API completely and making it deprecated on the REST layer (the parser would simply ignore it).
cc @nknize
The text was updated successfully, but these errors were encountered: