autophagy opened a new pull request, #26121: URL: https://github.com/apache/flink/pull/26121
## What is the purpose of the change Currently, `ResolvedSchema` is not supported in the Python Table API. This PR introduces it, as well as adding `get_resolved_schema()` to `Table` and replaces `get_table_schema()` in `TableResult` with `get_resolved_schema()`, similar to ba5b122de892a6919ff187c49f2d31e5e6a673f5. ## Brief change log - `ResolvedSchema` is introduced to Python Table API. - `Table.get_resolved_schema()` is added. - `TableResult.get_table_schema()` is replaced by `TableResult.get_resolved_schema()` ## Verifying this change Please make sure both new and modified tests in this PR follow [the conventions for tests defined in our code quality guide](https://flink.apache.org/how-to-contribute/code-style-and-quality-common/#7-testing). - This change is already covered by existing tests, such as sql and table environment api tests. - This change adds a test to the schema operation tests to verify the returned resolved schema is as expected. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes (in the sense that it changes the public api of `TableResult` and `Table`)) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (yes) - If yes, how is the feature documented? (docs) -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
