MartijnVisser commented on issue #3187: URL: https://github.com/apache/iceberg/issues/3187#issuecomment-928967812
For transparency purposes, this is what @twalthr shared with the mailing list on this topic: > I'm very sorry for the inconvenience that we have caused with our API > changes. We are trying our best to avoid API breaking changes. Thanks > for giving us feedback. > > There has been a reason why Table API was marked as `@PublicEvolving` > instead of `@Public`. Over the last two years, we have basically rewritten > the entire API [1] to digest the Blink merge and making the Table API > stable and ready for the future. We tried our best to give users 1-2 > releases time to upgrade their implementations whenever we deprecated > API but we were aware that this might cause frustration, but hopefully > for the greater good. We have reworked type system, Catalog API, schema, > source/sinks, functions and much more. Flink 1.14 will hopefully be the > last release with major API changes. We could also mark most Table API > interfaces as `@Public` in 1.15. > > For your mentioned incompatibility, I agree that the change from > CatalogTable to ResolvedCatalogTable was not very nice. Since > implementing a connector is not straight forward, we were expecting that > not many users implement custom connectors. We therefore consider this > part as kind of "second level API" for which we can evolve quicker. A > `context.getCatalogTable().getSchema()` should still work for 1.12 and > 1.13, at least that was the goal. > > Thanks again for the feedback. It was a good reminder and we will pay > more attention to this. > > [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributions -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
