-
Notifications
You must be signed in to change notification settings - Fork 97
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
search_entities
API might be throttled
#206
Comments
We have been facing the same issue. We are dealing with similar amount of entities i.e. entities > 20k |
Could you please supply your method parameters. I believe the discovery endpoint has a limit of 10k per page so it's normal to expect paging in the API. |
These are my supply parameters "("*", search_filter=filter_setup, limit=1000, starting_offset=0)". I noticed that irrespective of what supply parameters are given the generator object actually returns all the values so I have been turning the generator object directly to a list and getting all 18K entities at once. Here is the error message I received: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
I was unable to replicate your error and I made >20K individual requests to an endpoint. Are you going through a proxy? A quick google of your error brought up a related issue with the az cli. Perhaps look into your proxy config and library versions of the dependencies.
|
Describe the bug
When there's a large amount of purview entities (currently we have > 20K), the
search_entities
API might have this error:Seems in the code, the
search_entities
API keeps calling the query API, and looks like purview has some enforced throttling in the backend which results this error.The text was updated successfully, but these errors were encountered: