-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement query language #14
Comments
I've done a lot of brainstorming on this this week and this is a highly complex topic.
(I think my earlier time estimate can be at least doubled or tripled) I'm taking a step back a step back at this stage and postponing such an implementation until a later point in time where it becomes more relevant. I think at this stage (with no real users yet) it's more prudent to focus on searching with the lower-level API that is already implemented, and optimize and document that API. |
Coming back to this topic: I did some further investigation and came to the conclusion that the current lower-level API is insufficient for proper search and querying. Expressing a higher-level search question with this API is simply too complex. So a higher-level search interface (API) is something that can not be avoided anymore. |
A higher-level API has now been implemented, it's still short of a fully-fledged query language, but it makes this less of a priority. |
The query language has been implemented, they may still be some loose ends but most of it works nicely. |
Implement a higher-level query language. Effectively parsing and translating high-level queries into calls to lower-level search methods. One major challenge is to find in what parts of a query to execute before others, in such a way that the search space is as small as possible (= quickest search results and most performant).
Depends on:
This will take significant time to implement (wild guess: 150 hours).
The text was updated successfully, but these errors were encountered: