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

Update HdfsFile.md #354

Merged
merged 1 commit into from
Jan 8, 2025
Merged

Update HdfsFile.md #354

merged 1 commit into from
Jan 8, 2025

Conversation

JeremyXin
Copy link
Contributor

In the BaseSinkConfig.java code, there is a configuration key called “remote_user”, but it is not shown in the front-end documentation. This configuration is useful when you need to control read and write (access rights) to HDFS by specific users.

I have encountered the following errors in actual use: Caused by: org.apache.hadoop.ipc.RemoteException: Permission denied: user=root, access=WRITE, inode="/tmp/seatunnel/seatunnel". By setting remote_user="xxx" as the specified user in the HdfsFile of the Sink section, the above problems can be solved.

Therefore, the configuration key should be displayed in the front-end documentation.

In the BaseSinkConfig.java code, there is a configuration key called “remote_user”, but it is not shown in the front-end documentation. This configuration is useful when you need to control read and write (access rights) to HDFS by specific users.

I have encountered the following errors in actual use: Caused by: `org.apache.hadoop.ipc.RemoteException: Permission denied:  user=root, access=WRITE, inode="/tmp/seatunnel/seatunnel"`. By setting remote_user="xxx" as the specified user in the HdfsFile of the Sink section, the above problems can be solved. 

Therefore, the configuration key should be displayed in the front-end documentation.
Copy link
Contributor

@davidzollo davidzollo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1
good job

@davidzollo davidzollo merged commit bd6adcc into apache:main Jan 8, 2025
1 check passed
@davidzollo
Copy link
Contributor

Since this might be your first contribution, I think we can have a more in-depth communication to help you get familiar with SeaTunnel. Feel free to contact me on LinkedIn (David Zollo) or WeChat (taskflow). When adding me, please let me know your GitHub ID. I'd be happy to create connection with you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants