Github user ChristopheSchmitz commented on the issue:
https://github.com/apache/spark/pull/14897
@cloud-fan thanks for pointing that out. Those closed-source tools might
need some time to be updated. Nothing I can do on that front :(
As this fully qualified name constraints is
Github user ChristopheSchmitz commented on the issue:
https://github.com/apache/spark/pull/14897
I should add, I am using createGlobalTempView as I want to share the view
across all sessions, as described in
http://spark.apache.org/docs/2.1.0/sql-programming-guide.html#global
Github user ChristopheSchmitz commented on the issue:
https://github.com/apache/spark/pull/14897
Hi cloud-fan,
I am using global_temp because I have some view created with
createGlobalTempView() that I would need to access using some tools for which I
am configuring the database
Github user ChristopheSchmitz commented on the issue:
https://github.com/apache/spark/pull/14897
Hi there,
I am a bit puzzled by the golbal_temp database. Why do we need to provide a
qualified name to access the view? We can't even use the "USE global_temp"
