-
Notifications
You must be signed in to change notification settings - Fork 751
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
bug: delegation token parameter should be renamed when using WebHDFS as storage #16742
Comments
It seems that this issue is related to OpenDAL. After checking reproducable via OpenDAL API, let me report to OpenDAL. |
Thank you @jason-heo for this. Maybe we can also accpet |
This change should be simple that parse |
Hello, @Xuanwo If my understanding is correct, to resolve this isssue one needs to replace Could you point me out which source code should be modified for this issue? I tried to find
Sorry, my team's task priority has been changed. Thanks. |
I reviewed the issue, and it seems the solution lies in the WebhdfsBuilder implementation in OpenDAL. I have a proposed fix in the PR: https://github.com/apache/opendal/pull/5342/files |
Hi, please fix the builder at databend side instead. |
Hi, thanks for pointing that out! Could you please guide me on where exactly the builder is located on the Databend side? A pointer to the relevant file or module would be helpful. Also what is the rationale behind keeping the auth value as delegation_token on the OpenDAL side? |
Oh, I see. Databend does use |
This issue will be fixed by apache/opendal#5342 |
Search before asking
Version
What's Wrong?
Hello, Im new to Databend.
I'm trying to test Databend with my data on secure hadoop.
I've setup Query node as describe in Deploying with HDFS using WebHDFS
My current setting is like this:
When I run
INSERT INTO
I got an error:I think
delegation_token
should be renamed todelegation
.You can see not
delegation_token
butdelegation
on WebHDFS REST API -> AuthenticationI've tested using
curl
and confirm that following url worked well.How to Reproduce?
Described above.
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: