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

Web console: add explore view #14602

Merged
merged 7 commits into from
Jul 21, 2023
Merged

Conversation

vogievetsky
Copy link
Contributor

This PR adds a simple, stateless, SQL backed, data exploration view to the web console. The idea is to let users explore data in Druid with point-and-click interaction and visualizations (instead of writing SQL and looking at a table). This can provide faster time-to-value for a user new to Druid and can allow a Druid veteran to quickly chart some data that they care about.

image

The view is self contained. There are only a handful of lines of code outside the /explore-view/ path, and only to hook the view into the router and header.

The view is accessible via the header bar here:

image

Copy link
Member

@clintropolis clintropolis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is rad 🤘

some general commentary on things i noticed (none are blockers since this is like totally new and marked as obviously experimental):

  • man this is slick 🚀
  • filter bar allows clicking ok when no filtering is set, which makes bad queries (side note, it might be nice to show the bad query it tried to run to help us help you debug stuff, i had to dig around in my broker logs to figure out what was failing since i only saw the validation error message, but it wasn't obvious the query it was trying to run)
  • filter bar maybe could use hover text or some branding to indicate that it is in fact for filtering stuff
  • clicking 'show' on stuff that doesn't support grouping such as COMPLEX silently has an error and doesn't update visual, had to dig around in web-console errors to find this
  • same thing about trying to filter stuff that isn't supported for grouping
  • picking a different table in the dropdown doesn't clear current state (filters, charts, etc) idk if it should... but things like filters it probably makes sense because it seems likely the same columns wouldn't exist
  • changing the 'stack by' does not seem to always update the chart.. though maybe this only happens when it gets into some other sort of error state
  • did i mention how rad this was? 🎉
  • can has custom time granularity?
  • maybe something funny going on when trying to filter time, since it doesn't seem to stick with the range im trying to choose
  • definitely something funny going on when i try to pick an exact time interval, text box moves cursor to end and then cannot close if i can manage to type in fast enough to make the range i want
  • since there is a default time filter, should it show up on the filter bar, at least if you are not in table view?

i'm so hyped i'll approve this even with these issues. will keep playing with stuff trying to find things

@clintropolis
Copy link
Member

sweet looks like the things i ran into last time i tested have been fixed. I still can cause some silent errors that just have no indicator in the UI that something didn't work other than nothing changing, such as anything that would use a group query on a column type that isn't supported like json, but I haven't got it to run into any unrecoverable states yet.

🚀

Copy link
Member

@asdf2014 asdf2014 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

docs/tutorials/tutorial-msq-convert-spec.md Outdated Show resolved Hide resolved
Co-authored-by: Benedict Jin <asdf2014@apache.org>
@abhishekagarwal87 abhishekagarwal87 merged commit f5784e6 into apache:master Jul 21, 2023
74 checks passed
sergioferragut pushed a commit to sergioferragut/druid that referenced this pull request Jul 21, 2023
This PR adds a simple, stateless, SQL backed, data exploration view to the web console. The idea is to let users explore data in Druid with point-and-click interaction and visualizations (instead of writing SQL and looking at a table). This can provide faster time-to-value for a user new to Druid and can allow a Druid veteran to quickly chart some data that they care about.
AmatyaAvadhanula pushed a commit to AmatyaAvadhanula/druid that referenced this pull request Aug 1, 2023
This PR adds a simple, stateless, SQL backed, data exploration view to the web console. The idea is to let users explore data in Druid with point-and-click interaction and visualizations (instead of writing SQL and looking at a table). This can provide faster time-to-value for a user new to Druid and can allow a Druid veteran to quickly chart some data that they care about.
abhishekagarwal87 pushed a commit that referenced this pull request Aug 1, 2023
This PR adds a simple, stateless, SQL backed, data exploration view to the web console. The idea is to let users explore data in Druid with point-and-click interaction and visualizations (instead of writing SQL and looking at a table). This can provide faster time-to-value for a user new to Druid and can allow a Druid veteran to quickly chart some data that they care about.

Co-authored-by: Vadim Ogievetsky <vadim@ogievetsky.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants