[
https://issues.apache.org/jira/browse/DRILL-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501673#comment-16501673
]
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-394687539
What if the options were loaded into the JS form on first connection to the
web UI and cached? These settings don't change much, so setting a longer
cache timeout and refreshing cache on change would not be a resource drain.
This could be a file (maybe even JS like it is now) but not part of the
code base, it's generated from the system of record.
On Tue, Jun 5, 2018, 2:29 AM Arina Ielchiieva <notificati...@github.com>
wrote:
> @kkhatua <https://github.com/kkhatua>, we don't have that many options to
> have significant load on web server. I understand you want to make options
> page user-friendly but maintaining options descriptions separately from
> options is not a good idea. Developers definitely won't remember to update
> js file when adding new options. So at some point we'll end up with stale
> descriptions. I am sorry but I would rather have less-user friendly options
> page then implemented this way. Until we don't have better solution, you
> can add link to the Drill documentation where options are described on
> options page.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/drill/pull/1279#issuecomment-394609967>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AB1zUTWKtmKsAcEbMmTwqmBwRlTIIjKaks5t5jNlgaJpZM4UGO84>
> .
>
----------------------------------------------------------------
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:
us...@infra.apache.org
> 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
> Labels: ready-to-commit
> 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)
