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

Graphical query builder #8112

Closed
markwalkom opened this issue Aug 29, 2016 · 10 comments
Closed

Graphical query builder #8112

markwalkom opened this issue Aug 29, 2016 · 10 comments
Labels
Feature:KQL KQL Feature:New Feature New feature not correlating to an existing feature label impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:small Small Level of Effort release_note:enhancement

Comments

@markwalkom
Copy link
Contributor

Sense/Console is schway, but there's still a gap when users start on the Elastic journey as they need to understand at least some of the DSL. Having a graphical query builder where people can start with a basic query and then drill down into more complex things like aggregations would be fantastic.

Here is an example of how you can easily abstract the DSL out into reasonably easier to understand terms.

@pemontto
Copy link

+1

@markwalkom
Copy link
Contributor Author

You can +1 things on GH by just picking the + and smiley face icon at the top of the original post in the issue :)

@juerkan
Copy link

juerkan commented Sep 6, 2016

+1

@kobelb
Copy link
Contributor

kobelb commented Aug 7, 2018

/cc @elastic/kibana-discovery this seems to have an overlap with what we're doing with KQL/SQL, any sustained interest in this concept?

@lukasolson
Copy link
Member

Also related to @markharwood's work on sculptor. Yes, we definitely still have an interest in this concept.

@markharwood
Copy link
Contributor

I think the biggest advantage of a sculptor-like query builder would be to unify the 3 disparate ways criteria is managed today:
image

@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:KQL KQL Feature:New Feature New feature not correlating to an existing feature label and removed :Discovery labels Sep 16, 2018
@markharwood
Copy link
Contributor

Update - demo of how to "upgrade" a KQL or Lucene style query syntax into a graphical representation https://www.youtube.com/watch?v=eN_8rvonV4A

This conversion can
a) Make it easier to edit/unfold logic in the original textual format
b) Allow mixing with other criteria sourced from visualization selections into ORs ANDs etc.

@timroes timroes added Team:AppArch and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Feb 20, 2020
@elasticmachine
Copy link
Contributor

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

@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 2, 2021
@markharwood
Copy link
Contributor

markharwood commented Sep 6, 2021

The other major use for draggable query objects is that they could/should be draggable and droppable into a wide range of visualizations (line charts, maps, graph ...) as the user's chosen subjects of interest.
If users cannot drop their explicit choices of subject matter into a visualization then they are typically left with playing a limited form of lucky dip - seeing what the visualization throws up as the top 10 results from a choice of field. Top ten "discovery" like this might be useful to the clueless user but for those users with more of an idea about what subjects they want to see rendered and what queries define them, the ability to drop query objects into the visualizations is very important.

Sculptor_leadership_presentation

@exalate-issue-sync exalate-issue-sync bot added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels May 17, 2022
@ppisljar
Copy link
Member

ppisljar commented Aug 9, 2022

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.

@ppisljar ppisljar 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:KQL KQL Feature:New Feature New feature not correlating to an existing feature label impact:medium Addressing this issue will have a medium 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

9 participants