...@databricks.com
mailto:mich...@databricks.com, Cheng, Hao hao.ch...@intel.com
mailto:hao.ch...@intel.com, user@spark.apache.org
mailto:user@spark.apache.org user@spark.apache.org
mailto:user@spark.apache.org
Subject: Re: problem with HiveContext inside Actor
Akka actor are managed under a thread
...@databricks.com
mailto:mich...@databricks.com, Cheng, Hao hao.ch...@intel.com
mailto:hao.ch...@intel.com, user@spark.apache.org
mailto:user@spark.apache.org user@spark.apache.org
mailto:user@spark.apache.org
Subject: Re: problem with HiveContext inside Actor
Akka actor are managed under
@spark.apache.orgmailto:user@spark.apache.org
Subject: Re: problem with HiveContext inside Actor
Akka actor are managed under a thread pool, so the same actor can be under
different thread.
If you create HiveContext in the actor, is it possible that you are essentially
create different instance of HiveContext
Hi, Du
I am not sure what you mean triggers the HiveContext to create a database, do
you create the sub class of HiveContext? Just be sure you call the
HiveContext.sessionState eagerly, since it will set the proper hiveconf
into the SessionState, otherwise the HiveDriver will always get the
- dev
Is it possible that you are constructing more than one HiveContext in a
single JVM? Due to global state in Hive code this is not allowed.
Michael
On Wed, Sep 17, 2014 at 7:21 PM, Cheng, Hao hao.ch...@intel.com wrote:
Hi, Du
I am not sure what you mean “triggers the HiveContext to
...@intel.com
Cc: Du Li l...@yahoo-inc.com.invalidmailto:l...@yahoo-inc.com.invalid,
user@spark.apache.orgmailto:user@spark.apache.org
user@spark.apache.orgmailto:user@spark.apache.org
Subject: Re: problem with HiveContext inside Actor
- dev
Is it possible that you are constructing more than one
