[
https://issues.apache.org/jira/browse/DRILL-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482908#comment-16482908
]
ASF GitHub Bot commented on DRILL-5735:
---------------------------------------
JohnOmernik commented on issue #1279: DRILL-5735: Allow search/sort in the
Options webUI
URL: https://github.com/apache/drill/pull/1279#issuecomment-390749252
I like what I am seeing here. This is a great usability step in helping
users in the web UI understand what options are available and how they work. I
like the filtering and the update in place.
I do think the hard coded descriptions in the JS will be problematic over
time. The descriptions will beed to be updated to stay in sync with the web
pages. This is why I suggested
https://issues.apache.org/jira/browse/DRILL-4699?jql=text%20~%20%22sys.options%22
Basically, this is a good UI front from what I am talking about in 4699,
however, we should find a way to make sys.options the system of record for the
options and their descriptions, and then use that to either fill this page, or
if that is not performant enough, use the sys.options to generate the js file
with descriptions at build time. (and the Website descriptions of options)
I love the UI work, I am worried about the data drift of managing the
sys.options.
John
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> UI options grouping and filtering & Metrics hints
> -------------------------------------------------
>
> Key: DRILL-5735
> URL: https://issues.apache.org/jira/browse/DRILL-5735
> Project: Apache Drill
> Issue Type: Improvement
> Components: Web Server
> Affects Versions: 1.9.0, 1.10.0, 1.11.0
> Reporter: Muhammad Gelbana
> Assignee: Kunal Khatua
> Priority: Major
> Fix For: 1.14.0
>
>
> I'm thinking of some UI improvements that could make all the difference for
> users trying to optimize low-performing queries.
> h2. Options
> h3. Grouping
> We can organize the options to be grouped by their scope of effect, this will
> help users easily locate the options they may need to tune.
> h3. Filtering
> Since the options are a lot, we can add a filtering mechanism (i.e. string
> search or group\scope filtering) so the user can filter out the options he's
> not interested in. To provide more benefit than the grouping idea mentioned
> above, filtering may include keywords also and not just the option name,
> since the user may not be aware of the name of the option he's looking for.
> h2. Metrics
> I'm referring here to the metrics page and the query execution plan page that
> displays the overview section and major\minor fragments metrics. We can show
> hints for each metric such as:
> # What does it represent in more details.
> # What option\scope-of-options to tune (increase ? decrease ?) to improve the
> performance reported by this metric.
> # May be even provide a small dialog to quickly allow the modification of the
> related option(s) to that metric
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
