Repository navigation
Replies: 4 comments
|
Thank you for sharing the lineage experiment, especially for distinguishing CBM's graph search from your additional correlation logic. A small public example showing the source repositories, query, expected lineage, and observed result would be useful evidence. We have not validated the reported token reduction or cross-repository accuracy, but the concrete workflow is valuable feedback. |
|
Thank you for sharing the lineage work. Checking back on the public-example request: if you have a shareable sample now, the expected lineage alongside the CBM queries and your extra correlation step would be the most useful follow-up. There is no new validation result from the project to report here, and no need to share private datasets. |
|
Thank you again for the discussion. If you now have a public sample, the expected lineage, CBM queries, and additional correlation step would help assess the result. |
|
HI @DeusData , here is the repo with my initial base solution. I have used deterministic code and queries to extract required information from the DB. you can find all the details in the markdown file. I had run this solution on smaller repos and it give me exact output I was expecting. https://github.com/rajeshgmv/GItbased-DataLineage/tree/main Sample output file can be found at - [lineage_output/cross-boundary-lineage.md] Please note that this basic code which helped to derive DB/file level lineage along with application level. I have tested this solution with gemini flash 2.5 and 3. Flash 2.5 couldn't infer some of the alias but 3 gave me the exact output I was expecting. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have been building a personal multi-agent data lineage discovery project using CBM-MCP graph search to generate focused context for each agent.
CBM-MCP, combined with additional preprocessing and correlation logic, has helped reduce the amount of source code passed to the agents and lower token usage.
The results have been promising so far with public sample repositories, including cross-repository data flows. I am continuing to validate and improve the solution.
I will replicate the same for GUI based ETL tool such as informatica , optim, validate and provide feedback.
All reactions