[
https://issues.apache.org/jira/browse/HIVE-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465624#comment-16465624
]
Rui Li commented on HIVE-18533:
-------------------------------
Hi [~stakiar], for SparkLauncherSparkClient, how about we use a thread to wait
on the countdown latch and return a FutureTask like we did in
SparkSubmitSparkClient? I think it makes the two clients more consistent and
it's easier than implementing a custom Future. For example, when
{{Future::cancel}} is called, threads waiting on {{Future::get}} should
immediately be unblocked, and {{Future::isCancelled}} should return true. We
don't have to worry about breaking these contracts if we use FutureTask. What
do you think?
> Add option to use InProcessLauncher to submit spark jobs
> --------------------------------------------------------
>
> Key: HIVE-18533
> URL: https://issues.apache.org/jira/browse/HIVE-18533
> Project: Hive
> Issue Type: Improvement
> Components: Spark
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Attachments: HIVE-18533.1.patch, HIVE-18533.2.patch,
> HIVE-18533.3.patch, HIVE-18533.4.patch, HIVE-18533.5.patch,
> HIVE-18533.6.patch, HIVE-18533.7.patch, HIVE-18533.8.patch,
> HIVE-18533.9.patch, HIVE-18533.91.patch, HIVE-18831.93.patch
>
>
> See discussion in HIVE-16484 for details.
> I think this will help with reducing the amount of time it takes to open a
> HoS session + debuggability (no need launch a separate process to run a Spark
> app).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
