Lineage Capture Trade-offs: A Case Study in DuckDB

2 [3,4] a2 rid b1 b2 rid 2 1Figure 1: This figure shows the three lineage capture approaches evaluated in this paper on the query = 2,count( * ) ( ).(1) Query-Level: Rewrites the original query into + that augments lineage information with the output (Section 2.2). ( 2) Operator-Level: Transforms operators in the query plan to propagate lineage at the operator level, with the help of the Lineage Manager (LM) operator.Each LM operator removes lineage annotations from its child operator and, (except for the root) inserts a new ID column for tracking lineage in the parent operator (Section 2.3).(3) Function-Level: Modifies the implementation of physical operators to capture lineage artifacts-variables that track dependencies-during query execution (Section 2.4).