Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Nama yang sepenuhnya memenuhi syarat adalah ID resource peka huruf besar/kecil yang unik secara global yang dapat Anda gunakan dengan Dataplex Universal Catalog untuk merujuk ke resource Google Clouddan non- Google Cloud.Google Cloud
Misalnya, nama yang sepenuhnya memenuhi syarat digunakan untuk sistem yang mendukung
penyerapan otomatis
metadata dari Google Cloud. Jika Anda
mengatalogkan resource non-Google Cloud
di Dataplex Universal Catalog, Anda dapat memberikan nama yang sepenuhnya memenuhi syarat saat Anda
membuat entri kustom yang merepresentasikan resource pihak ketiga tersebut.
Nama yang sepenuhnya memenuhi syarat terdiri dari awalan yang diikuti dengan
segmen yang dibatasi dengan titik. Panjang maksimum adalah 4.000 karakter.
Kelilingi segmen yang berisi karakter khusus, seperti titik dua, titik, dan spasi kosong, dengan tanda petik terbalik. Gunakan tanda petik ganda untuk menentukan tanda petik dalam segmen.
Format standar untuk Google Cloud resource
Tabel berikut mencantumkan format standar untuk nama yang sepenuhnya memenuhi syarat yang didukung untuk resource Google Cloud .
Anda dapat membuat format nama yang sepenuhnya memenuhi syarat kustom menggunakan awalan custom:. Format kustom tidak divalidasi, dan mungkin tidak kompatibel dengan fitur Dataplex Universal Catalog. Untuk mempermudah migrasi di masa mendatang,
buat format kustom yang serupa dengan format standar.
Resource yang dirujuk dalam pesan OpenLineage dengan namespace custom ditafsirkan sebagai nama yang sepenuhnya memenuhi syarat kustom.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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."]]
