hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nemon Lou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10890) Provide implementable engine selector
Date Thu, 11 Jun 2015 01:46:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581332#comment-14581332
] 

Nemon Lou commented on HIVE-10890:
----------------------------------

I'm a little confused by this.Here is my thoughts:
Instead of implementing an automatic engine selector framework,
I think the hard part is the strategy of choosing different execution engine.
MapReduce is getting old and there is a plan to remove it from hive 2.0 in the future(mentioned
by Alan).
Tez and Spark both are more generic parallel computing framework treated as the next generation
of MapReduce.
They're both good at dealing with DAGs and overlapping a lot.

> Provide implementable engine selector
> -------------------------------------
>
>                 Key: HIVE-10890
>                 URL: https://issues.apache.org/jira/browse/HIVE-10890
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Trivial
>
> Now hive supports three kind of engines. It would be good to have an automatic engine
selector without setting explicitly engine for execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message