A Data Source Dependency Analysis Framework for Large Scale Data Science Projects
Not on the map. Why?
Abstract (arXiv)
Dependency hell is a well-known pain point in the development of large software projects and machine learning (ML) code bases are not immune from it. In fact, ML applications suffer from an additional form, namely, "data source dependency hell". This term refers to the central role played by data and its unique quirks that often lead to unexpected failures of ML models which cannot be explained by code changes. In this paper, we present an automated dependency mapping framework that allows MLOps engineers to monitor the whole dependency map of their models in a fast paced engineering environment and thus mitigate ahead of time the consequences of any data source changes (e.g., re-train model, ignore data, set default data etc.). Our system is based on a unified and generic approach, employing techniques from static analysis, from which data sources can be identified reliably for any type of dependency on a wide range of source languages and artefacts. The dependency mapping framework is exposed as a REST web API where the only input is the path to the Git repository hosting the code base. Currently used by MLOps engineers at Microsoft, we expect such dependency map APIs to be adopted more widely by MLOps engineers in the future.
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 3 of its 15 references that are in the map. First posted on arXiv 15 Dec 2022.
Builds on
3 of 15 references.
References · 3
- 2022MLOps -- Definitions, Tools and Challengescited by 25
- 2021A Static Analysis Framework for Data Science Notebookscited by 4
- 2022Abstract Interpretation-Based Data Leakage Static Analysiscited by 3
Built on by
Not cited yet.