[ https://issues.apache.org/jira/browse/HIVE-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100014#comment-14100014 ]
Brock Noland commented on HIVE-7606: ------------------------------------ Nice work [~vkorukanti]! Which patch should go first this one or HIVE-7746? Or are they independent in terms of order? > Design SparkSession, SparkSessionManager [Spark Branch] > ------------------------------------------------------- > > Key: HIVE-7606 > URL: https://issues.apache.org/jira/browse/HIVE-7606 > Project: Hive > Issue Type: Task > Components: Spark > Reporter: Brock Noland > Assignee: Venki Korukanti > Attachments: HIVE-7606.1-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 (v6.2#6252)