[
https://issues.apache.org/jira/browse/SPARK-15032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270018#comment-15270018
]
Sagar commented on SPARK-15032:
-------------------------------
You are right! It is safer to create new session of executionHive while
creating JDBC session but I think the problem is that it terminates the
executionHive process, let me know if you figured out other way, I can work on
it.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
