Skip to content
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

Closed
avleen opened this issue Jul 15, 2015 · 9 comments
Closed
Labels
Feature:Query Bar Querying and query bar features impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort release_note:enhancement

Comments

@avleen
Copy link

avleen commented Jul 15, 2015

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:

type:web_log AND request_uri:/ | _aggs:terms _field:user_ip_address

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!

@rashidkpc
Copy link
Contributor

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

@rashidkpc rashidkpc changed the title Changing search language Extending search language Jul 16, 2015
@avleen
Copy link
Author

avleen commented Sep 11, 2015

Hi @rashidkpc! Just wondering if you folks had any more time to think about this? :)

@spalger spalger removed the discuss label Feb 6, 2017
@Bargs Bargs added the Feature:Query Bar Querying and query bar features label Feb 10, 2017
@Bargs
Copy link
Contributor

Bargs commented Feb 10, 2017

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.

@avleen
Copy link
Author

avleen commented Feb 13, 2017

Hi @Bargs , thanks for the update :)
Is there any existing discussion on this in a ticket somewhere?
My view on this might be simplistic, but in theory going from search -> aggregations could be easy.
Eg:

.es(log:web, response:200) | .agg(type:terms, field:host, size=50)

@Bargs
Copy link
Contributor

Bargs commented Feb 14, 2017

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.

@avleen
Copy link
Author

avleen commented Feb 14, 2017 via email

@Bargs
Copy link
Contributor

Bargs commented Mar 17, 2017

As promised #10789

@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed :Discovery labels Sep 16, 2018
@timroes timroes added Team:AppArch and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Mar 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

@lukasolson lukasolson changed the title Extending search language Extending search language to support aggregations and multi-phase queries Jun 1, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Jun 1, 2021
@vadimkibana
Copy link
Contributor

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.

@vadimkibana vadimkibana closed this as not planned Won't fix, can't repro, duplicate, stale Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Query Bar Querying and query bar features impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort release_note:enhancement
Projects
None yet
Development

No branches or pull requests

8 participants