hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-7606) Design SparkSession, SparkSessionManager [Spark Branch]
Date Sun, 17 Aug 2014 23:48:19 GMT


Hive QA commented on HIVE-7606:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 5917 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed

This message is automatically generated.


> Design SparkSession, SparkSessionManager [Spark Branch]
> -------------------------------------------------------
>                 Key: HIVE-7606
>                 URL:
>             Project: Hive
>          Issue Type: Task
>          Components: Spark
>            Reporter: Brock Noland
>            Assignee: Venki Korukanti
>         Attachments: HIVE-7606.1-spark.patch, HIVE-7606.2-spark.patch
> In this JIRA we'll design two interfaces:
> * SparkSessionState
> * SparkSessionPoolManager
> and then once that is agreed upon we'll design two implementations:
> * SparkSessionStateImpl
> * SparkSessionPoolManagerImpl
> the form and function of these will be similar to the Tez equivalents. However, TezSessionState
provides some implementation which SparkClient already provides (refreshLocalResources*).
Let's keep SparkSessionState lightweight and not remove functionality from SparkClient. The
scope of this jira is just to create the shells and basic functionality. The implementations
in this jira should be able to:
> * Share a SparkSessionImpl across queries
> * Defining when a session can be re-used
> * Take ownership of SparkContext objects (Note we can only have a single SC until SPARK-2243
is resolved)

This message was sent by Atlassian JIRA

View raw message