[
https://issues.apache.org/jira/browse/HIVE-7330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081821#comment-14081821
]
Chengxiang Li commented on HIVE-7330:
-------------------------------------
Hi, [~chinnalalam], From the design doc, SparkTask should be a quite thin layer
which take SparkWork as input and use SparkClient to execute it. SparkClient is
the one who would load configurations, ship local resources, submit spark job,
and monitor job status. It seems your patch only use SparkClient to load
configurations, and move others functions to SparkTask, do you have any good
reasons for this?
> Create SparkTask
> ----------------
>
> Key: HIVE-7330
> URL: https://issues.apache.org/jira/browse/HIVE-7330
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Xuefu Zhang
> Assignee: Chinna Rao Lalam
> Attachments: HIVE-7330-spark.patch, HIVE-7330.1-spark.patch
>
>
> SparkTask handles the execution of SparkWork. It will execute a graph of map
> and reduce work using a SparkClient instance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
