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

Adding Kerberos for Enterprise #1481

Open
Maksllo opened this issue Jul 31, 2024 · 2 comments
Open

Adding Kerberos for Enterprise #1481

Maksllo opened this issue Jul 31, 2024 · 2 comments

Comments

@Maksllo
Copy link

Maksllo commented Jul 31, 2024

Hello, I am trying to create a pipeline for a large company and I encountered issues as the product does not support Kerberos for integration with Hive at all. Can you please advise if there are plans to add Kerberos and which direction I should look in order to do it myself? Also, can you explain how the product will work if I specify waggle-dance in the metastore?

@baumandm
Copy link
Contributor

Hey @Maksllo, I can't help with Kerberos, but we are using Waggle Dance as the metastore with the built-in HMSMetastoreLoader, and it works exactly as expected.

Since Waggle Dance implements the Hive Metastore API itself, all the metastores features will work in Querybook without any modifications needed.

@Maksllo
Copy link
Author

Maksllo commented Aug 20, 2024

Hey @Maksllo, I can't help with Kerberos, but we are using Waggle Dance as the metastore with the built-in HMSMetastoreLoader, and it works exactly as expected.

Since Waggle Dance implements the Hive Metastore API itself, all the metastores features will work in Querybook without any modifications needed.

Hello @baumandm , thank you for your message. I have made progress in connecting to Hadoop Kerberos. Could you clarify one question for me? When our users receive data from the metastore in the data warehouse, they see different data in Hue (only what is accessible to them). As I understand it, querybook (QB) operates on a completely different logic, and I may not be able to configure it so that only the user's data is displayed in the "tables" tab of the interface. If I am mistaken, could you please explain in more detail how this works? For example, I do not understand two things: 1) Why are the metastores separated so distinctly (why is it not done like in Hue)? 2) What is the purpose of specifying the metastore in the engine?

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

No branches or pull requests

2 participants