You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Gyorgy Gal (Jira)" <ji...@apache.org> on 2025/11/10 17:13:02 UTC

[jira] [Updated] (LIVY-651) Provide a approach to get "owner" inside spark application

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

Gyorgy Gal updated LIVY-651:
----------------------------
    Fix Version/s: 0.10.0
                       (was: 0.9.0)

This issue has been moved to the 0.10.0 release as part of a bulk update. If you feel this is moved out inappropriately, feel free to provide justification and reset the Fix Version to 0.9.0.

> Provide a approach to get "owner" inside spark application
> ----------------------------------------------------------
>
>                 Key: LIVY-651
>                 URL: https://issues.apache.org/jira/browse/LIVY-651
>             Project: Livy
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 0.6.0
>            Reporter: Xilang Yan
>            Priority: Major
>             Fix For: 0.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When impersonation is disabled, hadoop UGI user will always be livy server user, there is no way to get actually owner user in spark application.
> This issue is to fix this problem by add a "spark.livy.owner" property to spark context. Spark application code can get this property if needed.
> Actually, we use this way to control Spark SQL permissions. We use a spark.sql.extensions to get owner and decide whether operation is allowed. Spark application is submitted to YARN using hive user, this will make Spark SQL permission modelĀ  exactly the same with hive(Sentry) permission model.



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