cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Governance
Join discussions on data governance practices, compliance, and security within the Databricks Community. Exchange strategies and insights to ensure data integrity and regulatory compliance.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Service Principal Canโ€™t Access Full Query History via queryHistory/list API

lio-illumex
New Contributor

I have a weird issue with Databricks.
I'm using the query history API:
https://docs.databricks.com/api/workspace/queryhistory/list
When I'm using the API with Personal Access Token, it works great.

When i'm using the API with Service Principal, i'm getting only the history of the service principal.
I made sure that Service Principal has "Can Manage" Permission to the SQL Warehouse.
In addition, I added the Service Principal to the "admins" group but it didn't help.

This is very critical for one of our customers.

Thanks!

5 REPLIES 5

SP_6721
Honored Contributor

Hi @lio-illumex ,

Have you applied the filter while making the API call?
Try adding all target user IDs to the filter_by.user_ids field in your request bodyโ€”this might help retrieve the full query history you're expecting.

nayan_wylde
Honored Contributor III

@lio-illumex I think the API gets a paginated response. you need to hit the API recursively untill it reached the last page. Loop in until you get next_page_token. I would say the best way is to use the databricks SDK. It is simpler then the APIs.

https://databricks-sdk-py.readthedocs.io/en/stable/workspace/sql/query_history.html

 

jhonm_839
New Contributor III

The Query History API is scoped to the calling identity, so even with admin rights, service principals can only access their own queriesโ€”cross-user access isn't supported.

shkolar
New Contributor II

@SP_6721 I don't filter by user ids in both scenarios, it shouldn't matter
@nayan_wylde I also tried with the SDK but it's the same API call behind the scenes. I made sure it's not a pagination issue.
@jhonm_839 This is so weird. PAT and SP have the same admin rights.... and the admin PAT can see the SP queries.... I don't understand how it's not possible the other way around

nayan_wylde
Honored Contributor III

Is your workspace Unity Catalog Enabled? If yes try to give the SPN metastore admin permissions. Hopefully it should resolve the issue.