Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Different delegationUID for every user in JDBC connections
Added on November 20, 2018 6:03PM
Likes: 1
Replies: 2
Tomas
Registered, Neuron 2022 Posts: 121 ✭✭✭✭✭✭
Hi,
is it possible in DSS 5 set up separate delegationUID ( Impala specific JDBC property) for every user? The property can be set from system variables, but I dont know how to set it to the current user's name.
Something like this: for users in DSS "abc1234", "xyz2345" I would like to use their user ID's in the jdbc property, so when user "abc1234" runs the query against Impala, the JDBC connection string will contain delegationUID=abc1234, when user "xyz2345" runs the query, DSS opens a new connection with delegationUID=xyz2345
I noticed that there is a credentials option on the connection as well, but I think it does not fit in, when the Kerberos authentication is in place and the dssuser is using impersonation.
Thanks
is it possible in DSS 5 set up separate delegationUID ( Impala specific JDBC property) for every user? The property can be set from system variables, but I dont know how to set it to the current user's name.
Something like this: for users in DSS "abc1234", "xyz2345" I would like to use their user ID's in the jdbc property, so when user "abc1234" runs the query against Impala, the JDBC connection string will contain delegationUID=abc1234, when user "xyz2345" runs the query, DSS opens a new connection with delegationUID=xyz2345
I noticed that there is a credentials option on the connection as well, but I think it does not fit in, when the Kerberos authentication is in place and the dssuser is using impersonation.
Thanks
Answers
-
Hi,
In the MUS settings, you can set DSS user -> Unix user + Hadoop user mapping rules.
You cannot set Impala-specific rules, i.e. the rules you define in MUS settings apply to YARN, Hive and Impala at once. -
It is a different question. The MUS is fine, the DSS runs the Hadoop, YARN jobs in the context of the user (using impersonation). But the JDBC connection is different topic I think - because I remember when there was no option to define user-specific settings on JDBC connection level - so I assume DSS was using just one pool of the (same) connections (created by same settings).
Now as there is a possibility to choose User/Global for credentials I think DSS can handle internally for every user a different pool of connection(s). So I was curious, that if it would be possible to open for every user a connection with different parameter in the URI.
It would be a good feature, I hope it will be implemented in the next versions.
