Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Os nomes totalmente qualificados são identificadores de recursos globalmente exclusivos que diferenciam maiúsculas de minúsculas
e podem ser usados com o Catálogo Universal do Dataplex para se referir a recursos do Google Cloud
e de terceiros.Google Cloud
Por exemplo, nomes totalmente qualificados são usados para sistemas que oferecem suporte à ingestão automática de metadados do Google Cloud. Se você catalogar seus recursos nãoGoogle Cloud no Dataplex Universal Catalog, poderá fornecer nomes totalmente qualificados ao criar as entradas personalizadas que representam esses recursos de terceiros.
Os nomes totalmente qualificados são compostos de um prefixo seguido por segmentos delimitados com pontos. O tamanho máximo é de 4.000 caracteres.
Coloque crases em volta de segmentos que contêm caracteres reservados, como dois-pontos, pontos e espaços em branco. Use crases duplas para especificar uma
crase em um segmento.
Formatos predefinidos para recursos Google Cloud
As tabelas a seguir listam os formatos predefinidos para nomes totalmente qualificados que são compatíveis com recursos Google Cloud .
É possível criar um formato de nome totalmente qualificado personalizado usando o prefixo custom:. Os formatos personalizados não são validados e podem não ser compatíveis com os recursos do Dataplex Universal Catalog. Para facilitar a migração futura,
crie formatos personalizados semelhantes aos predefinidos.
Os recursos referenciados em mensagens do OpenLineage com o namespace custom são interpretados como nomes totalmente qualificados personalizados.
[[["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-19 UTC."],[[["\u003cp\u003eFully qualified names are unique, case-sensitive identifiers used in Dataplex to refer to resources within Google Cloud and other external systems.\u003c/p\u003e\n"],["\u003cp\u003eThese identifiers consist of a prefix followed by dot-delimited segments and must not exceed 4,000 characters in length.\u003c/p\u003e\n"],["\u003cp\u003ePredefined formats are provided for numerous services like BigQuery, Cloud Storage, Spanner, and others to standardize the structure of fully qualified names.\u003c/p\u003e\n"],["\u003cp\u003eSegments containing reserved characters (colons, dots, whitespace) should be enclosed in backticks, and double backticks should be used for backticks within a segment.\u003c/p\u003e\n"],["\u003cp\u003eUsers can create custom fully qualified name formats using the \u003ccode\u003ecustom:\u003c/code\u003e prefix, but these formats aren't validated and might not be compatible with all Dataplex features.\u003c/p\u003e\n"]]],[],null,["# Fully qualified names are globally unique, case-sensitive resource identifiers\nthat you can use with Dataplex Universal Catalog to refer to Google Cloud\nand non-Google Cloud resources.\n\nFor example, fully qualified names are used for systems that support the\n[automatic ingestion](/dataplex/docs/catalog-overview#supported-sources)\nof metadata from Google Cloud. If you\n[catalog your non-Google Cloud resources](/dataplex/docs/ingest-custom-sources)\nin Dataplex Universal Catalog, you can provide fully qualified names when you\ncreate the custom entries that represent those third-party resources.\n\nFully qualified names are composed of a prefix followed by\nsegments delimited with dots. The maximum length is 4,000 characters.\nSurround segments that contain reserved characters, such as colons, dots,\nand whitespace, with backticks. Use double backticks to specify a\nbacktick within a segment.\n\nPredefined formats for Google Cloud resources\n---------------------------------------------\n\nThe following tables list the predefined formats for fully qualified names that\nare supported for Google Cloud resources.\n\n### BigQuery\n\n### BigQuery sharing (formerly Analytics Hub)\n\n### Bigtable\n\n### Cloud SQL for MySQL\n\n### Cloud SQL for PostgreSQL\n\n### Cloud Storage\n\n### Dataplex Universal Catalog\n\n\n| **Caution:** The ingestion of Dataplex Universal Catalog entities under lakes and zones into Data Catalog (including those created as the output of Dataplex Universal Catalog Discovery) is [deprecated](/dataplex/docs/deprecations) and will stop functioning by September 30, 2025. External tables in BigQuery that are published by Discovery will be ingested into Dataplex Universal Catalog as entries.\n\n\u003cbr /\u003e\n\n### Dataproc Metastore\n\n### Looker\n\n### Pub/Sub\n\n### Spanner\n\n### Vertex AI\n\nPredefined formats for non-Google Cloud resources\n-------------------------------------------------\n\nThe following tables list the predefined formats for fully qualified names that\nare supported for third-party resources.\n\n### Apache Cassandra\n\n### Apache Hive\n\n### Apache Kafka\n\n### AWS Athena\n\n### AWS Redshift\n\n### AWS S3\n\n### AWS Glue\n\n### Azure Blob Storage\n\n### Azure Cosmos DB\n\n### Azure Data Explorer\n\n### Databricks File System\n\n### Generic File System\n\n### Hadoop Distributed File System\n\n### IBM DB2\n\n### IBM Informix\n\n### Microsoft SQL Server\n\n### MySQL\n\n### Oracle Database\n\n### PostgreSQL\n\n### Salesforce\n\n### Snowflake\n\n### Tableau\n\n### Trino\n\nCustom formats\n--------------\n\nYou can create a custom fully qualified name format by using the `custom:`\nprefix. Custom formats are not validated, and might not be compatible with\nDataplex Universal Catalog features. To ease future migration,\ncreate custom formats that are similar to predefined formats.\n\nResources that are referenced in OpenLineage messages with the namespace `custom` are\ninterpreted as custom fully qualified names."]]
