-
Notifications
You must be signed in to change notification settings - Fork 1.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
Cmd+enter shortcut to run query in Pinot data explorer query console #7359
Conversation
*Description* Add a shortcut (Cmd + Enter) that can be used to run the query when you are focused on the code editor in the pinot controller query console. Cmd + Enter is pretty standard in query application tools I've used before. Just a nice to have and makes running queries feel a bit easier.
Just adding docs about the cmd + enter shortcut I want to add as part of apache/pinot#7359
Codecov Report
@@ Coverage Diff @@
## master #7359 +/- ##
=============================================
- Coverage 71.65% 30.33% -41.32%
+ Complexity 3305 87 -3218
=============================================
Files 1515 1506 -9
Lines 74992 74644 -348
Branches 10903 10865 -38
=============================================
- Hits 53736 22645 -31091
- Misses 17629 49992 +32363
+ Partials 3627 2007 -1620
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for working on this!
Thanks @jackjlli - can you merge this in? (and also look at the documentation PR pinot-contrib/pinot-docs#58 if you have time) |
Description
Added a shortcut (Cmd + Enter) that can be used to run the query when you are focused on the code editor in the pinot controller query console.
Cmd + Enter is pretty standard in query application tools I've used before.
Just a nice to have and makes running queries feel a bit easier.
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)
No
Does this PR fix a zero-downtime upgrade introduced earlier?
No
Does this PR otherwise need attention when creating release notes? Things to consider:
No
Release Notes
n/a
-->
Documentation
pinot-contrib/pinot-docs#58