Reference documentation and code samples for the Data Lineage v1 API class Lineage.
Lineage is used to track data flows between assets over time. You can
create [LineageEvents][google.cloud.datacatalog.lineage.v1.LineageEvent]
to record lineage between multiple sources and a single target, for
example, when table data is based on data from multiple tables.
public static void BindService(ServiceBinderBase serviceBinder, Lineage.LineageBase serviceImpl)
Register service method with a service binder with or without implementation. Useful when customizing the service binding logic.
Note: this method is part of an experimental API that can change or be removed without any prior notice.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The `Lineage` class in the Data Lineage v1 API tracks data flows between assets, particularly when data from multiple sources contributes to a single target."],["Version 1.3.0 of the `Lineage` class is documented here, with links to other versions like 1.4.0 (latest), 1.2.0, 1.1.0, and 1.0.0 also being easily accessible."],["The `Lineage` class inherits from the `object` class and includes methods like `GetHashCode`, `GetType`, `MemberwiseClone`, and `ToString`."],["The `BindService` method can be used to create a service definition that can be registered with a server, which is crucial for implementing server-side handling logic."],["`BindService` can also be utilized to register service methods with or without implementation, allowing customization of the service binding logic."]]],[]]
