-
Notifications
You must be signed in to change notification settings - Fork 326
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
[super] Data Query Support #34
Comments
big +1 obviously. |
@pudo TODO: specify what this looks like in JSON (I need that to serialize it into the url for persistence at the very least ...) |
First steps on this are done, now its missing hash url serialization I think? |
As this includes sorting this now subsumes #23. |
* More natural in fact and we may as well go whole hog with ES structure.
* Also change so that query values are not automatically JSON.stringify-ied (bad idea since it leads to repeated jsonification of same value ...)
…h view updating. * Problem was in e.g. default demo that with new hash we were not matching on grid view and hence only displaying that (so we displayed both grid and graph which was nasty ...) * Fix this by better match on route. Also improve by using router.navigate on query update
I'm closing this now. Some backends don't support all of this but we have solid query support not in place in several and it is not clear what exactly remains. As new items arise we can open new tickets. |
…ticSearch (plus ref ElasticSearch in existing work). * Based on work here datopian/datahub#34
Query support would involve supporting things like:
This will clearly depend on backend capabilities.
Implementation
New Query model object attached to Dataset as query attribute #49 - New Query model object attached to Dataset as query attribute (we make into a Model so we can have event handlers)View support - query editor - Query editor view #53*
sort support in DataTable - done in 5fc4fa9Query Object Proposal
NB: It would be up to specific backends how to implement and support this query object. Different backends might choose to implement things differently or not support certain features.
Propose to base directly ElasticSearch query language. Query object would therefore have following key attributes:
Additions:
Examples
References
Simple 'DIY' Proposal
A query object will have the following attributes:
The text was updated successfully, but these errors were encountered: