independent user sessions with a multi-user spark sql thriftserver (Spark 1.1)

[Michael Allman <mi...@videoamp.com>]

Hello,

We're running a spark sql thriftserver that several users connect to with beeline. One limitation we've run into is that the current working database (set with "use <db>") is shared across all connections. So changing the database on one connection changes the database for all connections. This is also the case for spark sql settings, but that's less of an issue. Is there a way (or a hack) to make the current database selection independent for each beeline connection? I'm not afraid to hack into the source code if there's a straightforward fix/workaround, but I could use some guidance on what to hack on if that's required.

Thank you!

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

Re: independent user sessions with a multi-user spark sql thriftserver (Spark 1.1)

[Michael Armbrust <mi...@databricks.com>]

This is an unfortunate/known issue that we are hoping to address in the
next release: https://issues.apache.org/jira/browse/SPARK-2087

I'm not sure how straightforward a fix would be, but it would involve
keeping / setting the SessionState for each connection to the server.  It
would be great if you could share any findings on that JIRA.  Thanks!

On Mon, Nov 17, 2014 at 11:01 AM, Michael Allman <mi...@videoamp.com>
wrote:

> Hello,
>
> We're running a spark sql thriftserver that several users connect to with
> beeline. One limitation we've run into is that the current working database
> (set with "use <db>") is shared across all connections. So changing the
> database on one connection changes the database for all connections. This
> is also the case for spark sql settings, but that's less of an issue. Is
> there a way (or a hack) to make the current database selection independent
> for each beeline connection? I'm not afraid to hack into the source code if
> there's a straightforward fix/workaround, but I could use some guidance on
> what to hack on if that's required.
>
> Thank you!
>
> Michael
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@spark.apache.org
> For additional commands, e-mail: user-help@spark.apache.org
>
>