I support enabling row lineage by default primarily because of the ecosystem benefit that enables engines to rely on lineage without requiring users to opt in explicitly. This should generally apply to most engines and integrations.
However, as we know there are specific cases in the ecosystem—such as streaming engines producing equality deletes where we know row lineage cannot be preserved due to the expensive read and state management that would be involved. So that said, I think I agree with Peter that having a table property to indicate whether row lineage is accurate or not would be beneficial. I think this is preferable to expecting users to understand the nuances of different engines regarding lineage preservation. It provides users with a clear indication of what is happening in their table. Thanks, Amogh Jahagirdar
