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 just for preventing conflicts,
do you see any issue if I clone the project, and remove the check that prevents
from running "USE global_temp". Maybe the modification is more involved than
that. What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
