You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Muhammad Gelbana (JIRA)" <ji...@apache.org> on 2017/08/21 10:16:00 UTC

[jira] [Updated] (DRILL-5735) UI options grouping and filtering & Metrics hints

     [ https://issues.apache.org/jira/browse/DRILL-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Muhammad Gelbana updated DRILL-5735:
------------------------------------
    Description: 
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

  was:
I can think 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


> 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
>
> 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
(v6.4.14#64029)