-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Custom query types #623
Comments
I'm not really sure why this would require another moving part? Couldn't you instead make another query type as part of querySrv? Admittedly, the structure for adding query types could be improved, but I think that would be a better route than a proxy that parses and modifies elasticsearch requests. |
I wasn't truly sure it was the best way of doing things by adding the moving part either. It was intended to be there to add some additional query types for the old version of Kibana, which could continue to be used regardless of the version. In hind-sight it may be better to take that approach and make another query type part of querySrv. Thanks for the help. |
…a required arg is missing (elastic#623) * [Interpreter/Args] args get flag for required, throw error if a required arg is missing * add required flag for staticColumn * add required flag for mapColumn * add unit test for arg class * update functions doc generator to look for new flag * redo after interpreter arg resolve changes * error message for unnamed arg with no aliases
Hi Everyone,
I've been working with Kibana since the previous version in Ruby but I'm very new to html5 and javascript. In between Kibana and ES I've placed a web service which is functioning as somewhat of a proxy. Reason in doing this was to add some more complex queries where users could click a checkbox changing the search request from ///_search to ///_new_search where the web service would modify the default JSON query to something more complex, then post the new query to /_search and return the results.
Having the web service placed as a middle man may not be the best solution for this, but I was thinking it would be a nice feature if users could have some options for customizing their Search Queries.
Thanks,
Greg
The text was updated successfully, but these errors were encountered: