You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2016/06/01 04:48:12 UTC

[jira] [Commented] (SPARK-15032) When we create a new JDBC session, we may need to create a new session of executionHive

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

Yin Huai commented on SPARK-15032:
----------------------------------

I did a quick check today. Seems our current master it is fine. When we open a JDBC session, we indeed create the session state correctly. I am closing this jira.

> When we create a new JDBC session, we may need to create a new session of executionHive
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-15032
>                 URL: https://issues.apache.org/jira/browse/SPARK-15032
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Yin Huai
>            Priority: Critical
>
> Right now, we only use executionHive in thriftserver. When we create a new jdbc session, we probably need to create a new session of executionHive. I am not sure what will break if we leave the code as is. But, I feel it will be safer to create a new session of executionHive.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org