Re: [I] [SIP-203] Git-backed Version Control for Datasets in Apache Superset [superset]

["sebastianvillarroel (via GitHub)" <gi...@apache.org>]

sebastianvillarroel commented on issue #37427:
URL: https://github.com/apache/superset/issues/37427#issuecomment-4169901525

   Great SIP! As someone who has worked with Looker and several other BI tools, this is a gap I've thought about a lot. Versioning dataset definitions is a real step forward.
   
   One thing worth considering as a follow-up: knowing *what* changed in a dataset doesn't tell you *what broke downstream*. The propagation of a change is still manual and requires knowing where a dataset is used:  charts, dashboards, and models built on top of a modified virtual dataset can silently drift out of sync, and Git history alone doesn't surface that.
   
   Is there a vision for how Superset might eventually tackle change propagation, or is that seen as the domain of external lineage tooling?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org