[
https://issues.apache.org/jira/browse/DRILL-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500563#comment-16500563
]
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-394434022
So on the idea of UDFs, I don't think UDFs that are NOT shipped with the
product should be a concern of ours. Any UDF that ships with Drill needs
to be in the sys.functions.
Perhaps it would be cool to have a way to register UDFs in sys.function so
that folks who have UDFs that want to use sys.functions as a documentation
store can. Basically, a way in the UDF to add "company only" UDFs to the
sys.functions?
John
On Mon, May 21, 2018 at 2:04 PM, Kunal Khatua <notificati...@github.com>
wrote:
> @JohnOmernik <https://github.com/JohnOmernik> I agree. Single-source of
> truth for descriptions will help a long way.
> A similar ask for sys.functions is something that @arina-ielchiieva
> <https://github.com/arina-ielchiieva> had pointed to when we introduced
> syntax highlighting. That, of course, is more trickier due to dynamic UDFs.
> We can try to address that separately as a combined commit. For now, does
> this look sufficient within the context of the JIRA ?
>
> —
> 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-390751044>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AB1zUa8pjkYSCQ42g6pKwkZEEk9JyxRCks5t0w-6gaJpZM4UGO84>
> .
>
----------------------------------------------------------------
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)
