[SPARK-45454][SQL] Set the table's default owner to current_user #43264
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Could you re-trigger the failure pipelines, @wangyum ?
wangyum
force-pushed
the
SPARK-45454
branch
2 times, most recently
from
4c4566b to
7b811f2
Compare
wangyum
changed the title
wangyum
changed the title
Member
turboFei
pushed a commit
to turboFei/spark
that referenced
this pull request
Nov 6, 2025
…ent_user (apache#268) [SPARK-45454][SQL] Set the table's default owner to current_user ### What changes were proposed in this pull request? This PR sets the table's default owner to `CURRENT_USER`. ### Why are the changes needed? In thrift server mode, the owner of the table is inconsistent with the `SELECT CURRENT_USER();`, the owner of the table is always the user who started the thrift server. ### Does this PR introduce _any_ user-facing change? The table owner may be changed to `CURRENT_USER`. For example: ``` Before this PR: yumwangG9L07H60PK spark-3.5.0-bin-hadoop3 % bin/beeline -u "jdbc:hive2://localhost:10000/" -n test_table_owner -e "create table t(id int) using parquet; desc formatted t;" | grep Owner Connecting to jdbc:hive2://localhost:10000/ Connected to: Spark SQL (version 3.5.0) Driver: Hive JDBC (version 2.3.9) Transaction isolation: TRANSACTION_REPEATABLE_READ No rows selected (0.36 seconds) No rows selected (0.1 seconds) | Owner | yumwang | | 16 rows selected (0.055 seconds) Beeline version 2.3.9 by Apache Hive Closing: 0: jdbc:hive2://localhost:10000/ After this PR: yumwangG9L07H60PK spark-4.0.0-SNAPSHOT-bin-3.3.6 % bin/beeline -u "jdbc:hive2://localhost:10000/" -n test_table_owner -e "create table t(id int) using parquet; desc formatted t;" | grep Owner Connecting to jdbc:hive2://localhost:10000/ Connected to: Spark SQL (version 4.0.0-SNAPSHOT) Driver: Hive JDBC (version 2.3.9) Transaction isolation: TRANSACTION_REPEATABLE_READ No rows selected (0.719 seconds) No rows selected (0.335 seconds) | Owner | test_table_owner | | 16 rows selected (0.065 seconds) Beeline version 2.3.9 by Apache Hive Closing: 0: jdbc:hive2://localhost:10000/ ``` ### How was this patch tested? Unit test and manual test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#43264 from wangyum/SPARK-45454. Authored-by: Yuming Wang <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 4bad4b6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR sets the table's default owner to
CURRENT_USER.Why are the changes needed?
In thrift server mode, the owner of the table is inconsistent with the
SELECT CURRENT_USER();, the owner of the table is always the user who started the thrift server.Does this PR introduce any user-facing change?
The table owner may be changed to
CURRENT_USER.For example:
How was this patch tested?
Unit test and manual test.
Was this patch authored or co-authored using generative AI tooling?
No.