This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
You may have a general sense for how current your builds are, but as your pipeline increases in complexity and the dependency graph expands, it can be challenging to intuit whether part of your pipeline is up-to-date vis-à-vis the rest. In this task, we’ll take a break from our building narrative and head over to the Data Lineage graph to evaluate the recency of the datasets built in our flight_alerts_logic repository.
Having merged your feature branch into Master in your flight_alerts_logic repository, ctrl+click the Explore lineage button in the top right of your repository.
In Data Lineage, change the node coloring options in the top right to out-of-date.
At the bottom of the out-of-date node color legend, trying ticking and un-ticking the Data out-of date and Logic out-of-date options, noting the coloring differences. Navigate to the Data Lineage node coloring documentation and find the out-of-date item in the table for a description of the possible values.
This is a valuable node coloring option for determining whether your pipeline is universally up-to-date and where to look to correct build issues. In our case, nothing new has been built on the Master branch, so the Data in the nodes all appears current. However, there is new logic on the Master branch, so ticking the Logic box reveals datasets out of sync with the new logic.
Select all of the nodes on the graph with ctrl+a.
Click the “hammer” icon (“Manage builds”) in the collapsed side menu on the right.
Choose Selected dataset(s) only and then click the blue Next (View preview) button.
Click the blue Run build button at the bottom right of the screen. Once the process completes, the datasets (Data and Logic) will appear updated on your graph.