You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/05/27 23:01:00 UTC

[jira] [Updated] (SPARK-57109) Remove SYSTEM.SESSION from SYSTEM_PATH virtual schema

     [ https://issues.apache.org/jira/browse/SPARK-57109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SPARK-57109:
-----------------------------------
    Labels: pull-request-available  (was: )

> Remove SYSTEM.SESSION from SYSTEM_PATH virtual schema
> -----------------------------------------------------
>
>                 Key: SPARK-57109
>                 URL: https://issues.apache.org/jira/browse/SPARK-57109
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 4.2.0
>            Reporter: Serge Rielau
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.2.0
>
>
> Currently SYSTEM_PATH holds SYSTEM.BUILTIN and SYSTEM.SESSION.
> The purpose of the system path is to make access to system objects easy (especially in a future where we have more than one schema (e.g. SYSTEM.AI, or SYSTEM.ML, SYSTEM.GEO). The objects in SYSTEM.SESSION however are user defined.
> There is another reason to remove SYSTEM.SESSION from this as well: It seems liek a best practice to encourse references to temporray tables to be qualified by session, so they are not be confused or shadowed.
> In that case including system.session in the system path which is the most basic path one has to use, would be counter productive.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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