Expanded Lineage Not Visible Without Time Range Specification

Users were unable to view expanded lineage graphs beyond one degree of separation when querying lineage data through the API. The lineage API was returning no results unless a specific time range parameter was explicitly set, even though the parameter should have been optional or defaulted to a reasonable value.

You Might Be Asking:

• Why does my lineage query return empty results?
• How do I view multi-degree lineage relationships?
• What parameters are required for lineage API calls?

The issue has been resolved by fixing the API's handling of the time parameter and degree values. Users can now query lineage with multiple degrees of separation without requiring explicit time ranges.

When querying lineage via API:

# Query multi-degree lineage
lineage_result = graph.get_lineage(
    urn="urn:li:dataset:(...)",
    direction="DOWNSTREAM",  # or "UPSTREAM"
    degrees=[1, 2, 3]  # Multiple degrees now work correctly
)

Fixed in version v0.3.11. This was specifically related to handling too many degrees of lineage in the query response. The fix ensures proper pagination and result handling for complex lineage graphs.

• Lineage Overview
• GraphQL Lineage API