This document lists content limits and request quotas for Data Catalog. These limits apply to each Google Cloud Console project and organization and are shared across all applications and IP addresses.
The Data Catalog API enforces the following content limits:
|Maximum number of entries
(search results latency can increase when exceeded)
|MB per entry||10 MB|
|Maximum number of search results per page||1000|
|Fields per tag template||500|
|Length of field name in tag template||512 bytes|
|Length of resource name for a tag template||512 bytes|
|Length of string field in tag template||10000 bytes|
|Maximum number of enum values in a tag template||100|
|Tags per entry||1000|
|Maximum sum of two numbers:
|Maximum number of policy tags per taxonomy||100|
|Maximum number of taxonomies per project||40|
|Maximum depth of the policy tags tree
(100 policy tags per taxonomy still applies)
|Length of a policy tag name||200 bytes|
The QPM (queries per minute) of projects in an organization are added together to calculate the organization's QPM.
Data Catalog uses QPM quotas to prevent service overload rather than control request workload distribution among projects. Therefore, both project and organization have the same default QPM quotas. In other words, if an organization has multiple projects and the request workload of one of them approaches the default organization (and the same project) quota, this project may impact the potential workload of the other projects in the organization.
You can request to adjust organization and project quotas separately. For more information, see Working with quotas.
|QPM quota||Default value|
Currently, Data Catalog does not support quota increases.