Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spark][Bug]: The read and write authentication user are different in Spark when using mixed Iceberg format #1069

Closed
1 task done
hellojinsilei opened this issue Feb 7, 2023 · 1 comment
Labels
module:mixed-spark Spark module for Mixed Format priority:blocker security, data-loss, correctness, etc. type:bug Something isn't working
Milestone

Comments

@hellojinsilei
Copy link
Contributor

What happened?

When using mixed Iceberg format, Spark writer using the authentication user in SparkContext, but reader using the authentication user in arctic. So the written file cannot be read

image

Affects Versions

0.4.1

What engines are you seeing the problem on?

Spark

How to reproduce

step1: use mixed iceberg catalog and configure authenticated users in the arctic
step2: use different authentication users to write data using spark
step3: execute select

tips:The permission of the read authentication user is smaller than that of the write authentication user

Relevant log output

No response

Anything else

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@hellojinsilei hellojinsilei added type:bug Something isn't working module:mixed-spark Spark module for Mixed Format priority:blocker security, data-loss, correctness, etc. labels Feb 7, 2023
@hellojinsilei hellojinsilei added this to the Release 0.4.1 milestone Feb 7, 2023
@baiyangtx
Copy link
Contributor

The problem disappear after kyuubi restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module:mixed-spark Spark module for Mixed Format priority:blocker security, data-loss, correctness, etc. type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants