[
https://issues.apache.org/jira/browse/HIVE-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-3925:
-----------------------------------
Status: Open (was: Patch Available)
Changes in plan.xml files look susceptible. It seems with this change we will
begin to serialize FetchTask and FetchWork in our plan and will send it to
backend which is not required, since fetch task is executed from client itself.
Backend doesn't need to know about FetchTask. This unnecessarily bloats the
plan size. We need to figure out a way not to serialize fetch task in plans
sent to backend.
> dependencies of fetch task are not shown by explain
> ---------------------------------------------------
>
> Key: HIVE-3925
> URL: https://issues.apache.org/jira/browse/HIVE-3925
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Navis
> Attachments: HIVE-3925.4.patch.txt, HIVE-3925.D8577.1.patch,
> HIVE-3925.D8577.2.patch, HIVE-3925.D8577.3.patch
>
>
> A simple query like:
> hive> explain select * from src order by key;
> OK
> ABSTRACT SYNTAX TREE:
> (TOK_QUERY (TOK_FROM (TOK_TABREF (TOK_TABNAME src))) (TOK_INSERT
> (TOK_DESTINATION (TOK_DIR TOK_TMP_FILE)) (TOK_SELECT (TOK_SELEXPR
> TOK_ALLCOLREF)) (TOK_ORDERBY (TOK_TABSORTCOLNAMEASC (TOK_TABLE_OR_COL key)))))
> STAGE DEPENDENCIES:
> Stage-1 is a root stage
> Stage-0 is a root stage
> Stage: Stage-0
> Fetch Operator
> limit: -1
> Stage-0 is not a root stage and depends on stage-1.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
