You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/03/15 19:37:29 UTC
[GitHub] [flink] bowenli86 commented on issue #7848: [FLINK-10755][table]
Port external catalogs in Table API extension points to flink-table-common
bowenli86 commented on issue #7848: [FLINK-10755][table] Port external catalogs in Table API extension points to flink-table-common
URL: https://github.com/apache/flink/pull/7848#issuecomment-473416252
@twalthr re: The current catalog APIs are still intended to be used. What my team is thinking of rolling out unified catalog APIs is to build them separately and not touch existing ExternalCatalog APIs, and, upon it having full capabilities of existing catalog APIs, we can just do a switch. That's how we did it internally, and of course we can discuss if you have a different rollout plan. Anyway, the above was the background I had in mind then. With that, I was concerned that japicmp may report errors when changing a class's annotation from PublicEvolving to Deprecated, thus I did some testing locally and it seems to be fine.
I think it's ok to mark them as PublicEvolving. It's a bit hard to say as everything is moving around so fast in Flink table/SQL and our planned timeline.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services