Eugene Koifman created HIVE-14250:
-------------------------------------
Summary: Move FetchTask.initialize() in Driver from compile() to
execute()
Key: HIVE-14250
URL: https://issues.apache.org/jira/browse/HIVE-14250
Project: Hive
Issue Type: Bug
Components: Query Planning, Query Processor
Affects Versions: 2.1.0, 1.3.0
Reporter: Eugene Koifman
Driver.compile(String command, boolean resetTaskIds) has
// initialize FetchTask right here
if (plan.getFetchTask() != null) {
plan.getFetchTask().initialize(queryState, plan, null,
ctx.getOpContext());
}
It's not clear what the advantage of doing this in compile() vs
execute()/runInternal() is. One of the issues this causes is HIVE-14241.
HIVE-14241 has workaround but a much better fix is to move initialize() to
where it should be.
see
https://issues.apache.org/jira/browse/HIVE-14241?focusedCommentId=15379774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15379774
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
