goutamadwant commented on issue #11355: URL: https://github.com/apache/seatunnel/issues/11355#issuecomment-4932630709
@DanielLeens I would like to take a look and work on this as a design first item. My current thinking is to keep V1 as a lightweight runtime observability timeline, not a full persistent audit log. The first model would track the main schema change decision points: - source DDL or schema event arrival - normalization into a SeaTunnel SchemaChangeEvent - source table to target table resolution - schema change behavior policy decision - sink capability decision - final outcome like applied ignored skipped or failed I will also make the boundary clear with the related work in #11025, #11162, #11015 and #11328. This should consume those decisions instead of duplicating their logic. For retention, I am thinking bounded recent events per job/table for V1, with raw DDL either omitted or redacted/limited. Longer history or audit style storage can be a follow up if maintainers want that later. I can draft a STIP around this first before any implementation. Let me know your thoughts! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
