[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-06。"],[[["\u003cp\u003eData lineage is enabled per project, allowing automatic reporting for multiple systems within that project based on each system's product-level lineage control.\u003c/p\u003e\n"],["\u003cp\u003eAutomatic lineage tracking is supported for various systems, including BigQuery, Cloud Data Fusion, Cloud Composer, Dataflow, Dataproc, and Vertex AI, each with its own lineage control features.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the Data Lineage API has a billing impact, as it is enabled per project, and BigQuery Omni's lineage processing costs depend on the regions where it is performed.\u003c/p\u003e\n"],["\u003cp\u003eData lineage captures metadata about data movement, not the data itself, and it provides VPC-SC support but does not support Customer Managed Encryption Keys for lineage metadata.\u003c/p\u003e\n"],["\u003cp\u003eLineage node details might be empty if the resource is in another organization or the user isn't part of the organization hosting the resource.\u003c/p\u003e\n"]]],[],null,["# Data lineage considerations\n\nThis document provides information on data lineage compliance and limitations.\nData lineage is enabled on a per-project basis, not a\nper-system basis.\nThis means that after you enable the Data Lineage API, lineage information\ncan be automatically reported for multiple systems in the project, depending on\neach system's product-level lineage control.\n\nAutomatic lineage tracking is supported for the following systems:\n\n| **Important:** See [Supported systems](/dataplex/docs/about-data-lineage#lineage-supported-systems) for details on the support status of these systems. When a new system becomes available, depending on the level of that system's lineage control, the Data Lineage API can automatically start harvesting lineage data.\n\nBilling impact\n--------------\n\nWhen you enable the Data Lineage API on a project, review\nthe impact on your billing charges because the Data Lineage API is enabled\non a per-project basis (see the previous section for details).\nFor more information about how data lineage is charged, see\n[Dataplex Universal Catalog pricing](https://cloud.google.com/dataplex/pricing).\n\nFor BigQuery Omni, lineage processing\nis distributed to specific regions, and costs depend on the regions where\nthe processing is performed.\n\nData lineage compliance\n-----------------------\n\n- Data lineage records metadata about data movement but doesn't capture the data itself. See [data lineage information model](/dataplex/docs/about-data-lineage#information-model) and [Data Lineage API reference](/dataplex/docs/reference/data-lineage/rest) for details on what fields are included in the metadata.\n- Data lineage as part of Dataplex Universal Catalog offers VPC-SC support.\n- Dataplex Universal Catalog doesn't offer the ability to use Customer Managed Encryption Keys to protect the harvested lineage metadata.\n\nData lineage limitations\n------------------------\n\nWhen you select a node in the lineage graph, the node details side panel\nwill be empty when:\n\n1. the resources is located in another organization, or\n2. the user is not a member of the organization hosting the resource."]]
