[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-27 UTC."],[[["\u003cp\u003eDataproc Metastore services have a permanently assigned geographic location, known as a region, upon creation.\u003c/p\u003e\n"],["\u003cp\u003eLocation types include a single region, such as São Paulo, a custom-region, which is a pair of regions like Iowa and South Carolina, and a multi-region, like the United States.\u003c/p\u003e\n"],["\u003cp\u003eDataproc Metastore supports various features in both single-region and multi-region configurations, including Administrator Interface, Artifacts Cloud Storage bucket, Auxiliary versions, Backup/Restore, and more.\u003c/p\u003e\n"],["\u003cp\u003eSingle region services are available across multiple continents, such as Asia Pacific, Europe, Middle East, North America, and South America, each with several specific locations.\u003c/p\u003e\n"],["\u003cp\u003eMulti-regional and custom regions offer configurations combining specific regions, such as Iowa and South Carolina, for enhanced service deployment options.\u003c/p\u003e\n"]]],[],null,["When you create a Dataproc Metastore service, you permanently set\na geographic location for your service to reside in, otherwise known as a\nregion.\n\nYou can select from the following location types:\n\n- A *region* is a specific geographic place, such as São Paulo.\n- A *custom-region* ([Preview](/products#product-launch-stages)) is a specific pair of regions, such as Iowa and South Carolina.\n- A *multi-region* is a large geographic area, such as the United States, that contains two or more geographic places.\n\nSupported Dataproc Metastore features\n\nThe following table lists the Dataproc Metastore features\nthat are supported by single region and multi-regional configurations.\n\n| Feature | Single region | Multi-region |\n|-------------------------------------------------|---------------|---------------------------------------|\n| **Administrator Interface** | ✓ | ✓ |\n| **Artifacts Cloud Storage bucket** | ✓ | ✓ |\n| **Auxiliary versions** | ✓ | ✓ |\n| **Backup/Restore** | ✓ | ✓ |\n| **CMEK config** | ✓ | |\n| **Database type** | Spanner/MySQL | Spanner |\n| **Data Catalog sync** | ✓ | |\n| **Endpoint protocol (Thrift/gRPC)** | ✓ | ✓ |\n| **IAM policies on individual tables/databases** | ✓ | ✓ |\n| **Import/Export** | ✓ | ✓ |\n| **Kerberos** | ✓ | ✓ Only supported on the gRPC protocol |\n| **Private Service Connect** | ✓ | ✓ |\n| **Release channels** | ✓ | ✓ |\n| **Scaling config** | ✓ | ✓ |\n| **VPC-SC** | ✓ | ✓ |\n\nSingle region services\n\nDataproc Metastore is available in the following regions. For more\ninformation about regions and zones, see [Geography and regions](/docs/geography-and-regions).\n\nAsia Pacific\n\n| Region description | Region name |\n|--------------------|------------------------|\n| Taiwan | `asia-east1` |\n| Hong Kong | `asia-east2` |\n| Tokyo | `asia-northeast1` |\n| Seoul | `asia-northeast3` |\n| Mumbai | `asia-south1` |\n| Delhi | `asia-south2` |\n| Singapore | `asia-southeast1` |\n| Jakarta | `asia-southeast2` |\n| Sydney | `australia-southeast1` |\n| Melbourne | `australia-southeast2` |\n\nEurope\n\n| Region description | Region name |\n|--------------------|---------------------|\n| Warsaw | `europe-central2` |\n| Finland | `europe-north1` |\n| Madrid | `europe-southwest1` |\n| Belgium | `europe-west1` |\n| London | `europe-west2` |\n| Frankfurt | `europe-west3` |\n| Netherlands | `europe-west4` |\n| Zürich | `europe-west6` |\n| Milan | `europe-west8` |\n| Paris | `europe-west9` |\n| Turin | `europe-west12` |\n\nMiddle East\n\n| Region description | Region name |\n|--------------------|------------------------------------------------------------------------------------------------------------|\n| Tel Aviv | `me-west1` |\n| Dammam | `me-central2` Dataproc Metastore services created in `me-central2` can't be attached to Dataproc clusters. |\n\nNorth America\n\n| Region description | Region name |\n|--------------------|---------------------------|\n| Montréal | `northamerica-northeast1` |\n| Toronto | `northamerica-northeast2` |\n| Mexico | `northamerica-south1` |\n| Iowa | `us-central1` |\n| South Carolina | `us-east1` |\n| Northern Virginia | `us-east4` |\n| Columbus | `us-east5` |\n| Dallas | `us-south1` |\n| Oregon | `us-west1` |\n| Los Angeles | `us-west2` |\n| Salt Lake City | `us-west3` |\n| Las Vegas | `us-west4` |\n\nSouth America\n\n| Region description | Region name |\n|--------------------|----------------------|\n| São Paulo | `southamerica-east1` |\n| Santiago | `southamerica-west1` |\n\nMulti-regional services\n\nDataproc Metastore is available in the following multi-regions.\n\n| Region description | Region name |\n|--------------------|--------------------------------------------------------------|\n| `nam3` | Northern Virginia: `us-east4` and South Carolina: `us-east1` |\n| `nam7` | Iowa: `us-central1` and Northern Virginia: `us-east4` |\n| `nam10` | Iowa: `us-central1` and Salt Lake City: `us-west3` |\n| `nam11` | Iowa: `us-central1` and South Carolina: `us-east1` |\n| `eur3` | Belgium: `europe-west1` and Netherlands: `europe-west4` |\n| `eur5` | Belgium: `europe-west1` and London: `europe-west2` |\n\nCustom regions\n\nDataproc Metastore is available in the following predefined\ncustom regions configurations.\n\n| Region description | Region name |\n|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `US` | - Iowa: `us-central1` and South Carolina: `us-east1` - Oregon: `us-west1` and South Carolina: `us-east1` - Iowa: `us-central1` and South Carolina: `us-east1` |\n\nWhat's next\n\n- [Set up a multi-regional service](/dataproc-metastore/docs/multi-region-configurations)\n- [Update and delete a service](/dataproc-metastore/docs/manage-service)\n- [Use Apache Hive](/dataproc-metastore/docs/use-hive)"]]
