-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Extending search language to support aggregations and multi-phase queries #4437
Comments
More than a possibility! We're actually investigating new languages for describing how data should be extracted, transformed and viewed right now. I totally agree with you that this would be awesome |
Hi @rashidkpc! Just wondering if you folks had any more time to think about this? :) |
Timelion supports a query syntax like this now. We're starting to think about a replacement for the standard kibana query language at the moment, however we're mainly focused on search, not aggregations. |
Hi @Bargs , thanks for the update :)
|
It's not, but I'd like to write up a ticket soon. I'll try to remember to drop a reference here once I do. |
Thanks Matt :-)
…On Mon, Feb 13, 2017 at 7:07 PM Matt Bargar ***@***.***> wrote:
Is there any existing discussion on this in a ticket somewhere?
It's not, but I'd like to write up a ticket soon. I'll try to remember to
drop a reference here once I do.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4437 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAg7hXRVUzpzs4aV4qJh5PBoTcnhQ9LVks5rcPBZgaJpZM4FZY3e>
.
|
As promised #10789 |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment. |
Hi folks,
I'm interested in changing the search language use slightly. Currently the two options are to use Lucene Query Syntax or send JSON.
Is there any ability to change the language and provide, maybe, some kind of translation from what I want to JSON, which would then be executed?
Specifically, I'm interested in being able to write queries like this:
This would ideally go to the Visualize page and set up the request and the terms aggregation on that field.
I can easily map this query language to RISON, and if you folks have any pointers on how to integrate this into the existing UI, I'd love to hear them. I'm happy to do all the heavy lifting to make it work, if it's even a remote possibility, as it's our only major blocker to moving to Kibana 4.
Thanks!
The text was updated successfully, but these errors were encountered: