[
https://issues.apache.org/jira/browse/HIVE-24394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249893#comment-17249893
]
Johan Gustavsson commented on HIVE-24394:
-----------------------------------------
Thanks for taking a look at this and thank you for the feedback [~kgyrtkirk]. I
think that in normal cases using the standard HS2 web ui in combination with
the Tez UI make most queries very debug-able. The problem is that due to our
internal security policies, our end users can't be granted access to these
services. The only information end users can get access to is the query they
submit, the console log and the result of the query. On top of this most of the
users are submitting their queries through workflows using temporary
intermediate tables, so making a temporary change to do a one off explain print
is sometimes not easy for them. With this change we default to just have
explain printed in the console for all queries to make it easier to go back and
investigate unexpected behaviors.
> Enable printing explain to console at query start
> -------------------------------------------------
>
> Key: HIVE-24394
> URL: https://issues.apache.org/jira/browse/HIVE-24394
> Project: Hive
> Issue Type: Improvement
> Components: Hive, Query Processor
> Affects Versions: 2.3.7, 3.1.2
> Reporter: Johan Gustavsson
> Assignee: Jesus Camacho Rodriguez
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently there is a hive.log.explain.output option that prints extended
> explain to log. While this is helpful for internal investigations, it limits
> the information that is available to users. So we should add options to make
> this print non-extended explain to console,. for general user consumption, to
> make it easier for users to debug queries and workflows without having to
> resubmit queries with explain.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
