Quotas and limits

This document lists the quotas and limits for Data Catalog.

A quota restricts how much of a particular shared Google Cloud resource your Google Cloud project can use, including hardware, software, and network components. Quotas are part of a system that does the following:

  • Monitors your use or consumption of Google Cloud products and services.
  • Restricts your consumption of those resources for reasons including ensuring fairness and reducing spikes in usage.
  • Maintains configurations that automatically enforce prescribed restrictions.
  • Provides a means to make or request changes to the quota.

When a quota is exceeded, in most cases, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Google Cloud project and are shared across all applications and IP addresses that use that Google Cloud project.

To increase or decrease select quotas, use the Google Cloud console. For more information, see Requesting a higher quota.

There are also limits on resources. These limits are unrelated to the quota system. Limits cannot be changed unless otherwise stated.

By default, quotas and limits apply on a per-project basis.

Quotas

To calculate an organization's QPM (queries per minute), Data Catalog adds together the QPM of projects in the organization.

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.

To adjust organization and project quotas separately, see Requesting a higher quota.

QPM quota Default value
Read 6000
Write 1500
Search 1200

Data lineage quotas

The Data Lineage API enforces quotas for the following:

  • Read requests that only return the data
  • Write requests that create or change the data
  • Create Open Lineage

The Data Lineage API enforces data lineage quotas per project, per user, and per region. Default quotas are as follows:

QPM quota Default value
Read 1000
Write 6000
Open Lineage 3000

For example, you can submit up to 1000 GetProcess requests per minute in the test-project project in the us region before exceeding the quota.

Other quotas

Limits

The Data Catalog API enforces limits for entries, tags, and business metadata.

Entry limits

Limit Value
Maximum number of entry groups per organization across all locations 10k
Maximum number of entries per organization across all locations
(search results latency can increase when exceeded)
100M
Maximum number of entries per entry group 100k
MB per entry 10 MB
Maximum number of search results per page 1000

Tag limits

Limit Value
Fields per tag template 500
Length of a field name in a tag template 512 bytes
Length of a resource name for a tag template 512 bytes
Length of a string field in a tag template 10,000 bytes
Maximum number of enum values in a tag template 100
Tags per entry 1000
Maximum sum of two numbers:
  • Number of fields in all tags attached to an entry
  • Number of columns in the entry's optional schema
15,000
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)
5
Length of a policy tag name 200 bytes
Number of starred entries per user 200

Business metadata limits

Limit Value
Maximum number of data stewards per data entry 15
Maximum size of rich text in overview, excluding image sizes 100 KB
Total size of rich text including images 10 MB