fmorillo7694 commented on PR #236: URL: https://github.com/apache/flink-connector-aws/pull/236#issuecomment-5241832630
For reviewers' context: this PR is the first of a planned series adding Glue Schema Registry SQL formats. **Protobuf (`protobuf-glue`) and JSON (`json-glue`) follow-ups are already implemented** and stacked on this branch in my fork, to be submitted here once this PR lands: - Protobuf: https://github.com/fmorillo7694/flink-connector-aws/pull/2 - JSON: https://github.com/fmorillo7694/flink-connector-aws/pull/3 Validation done across the series, all against **real AWS Glue Schema Registry** (Localstack for the Kinesis data plane, per the existing e2e pattern): - 20 SQL-path e2e ITCases across the three formats: round-trips, complex types, NULL handling, ZLIB compression, BACKWARD/NONE/FULL compatibility modes, and the governance paths (`schema.autoRegistration = 'false'` against existing/missing schemas) - Schema evolution verified end-to-end for all three formats: v1 → v2 (add nullable field) registered under one schema name, then a single v2 SQL reader decoding mixed v1/v2 Kinesis records with NULL backfill for v1-era rows - CI green on all fork branches Sharing this so the design here can be reviewed with the full series in mind — happy to adjust scope or split differently if preferred. -- 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]
