Skip to content

Conversation

@autophagy
Copy link
Contributor

@autophagy autophagy commented Feb 17, 2025

What is the purpose of the change

Currently, the TablePipeline descriptor is not supported in the Pyflink Table API, so API methods such as insert_into on a table environment are subsequently not supported. This PR introduces the TablePipeline descriptor so that users can setup a table pipeline, explain it, execute it, etc. (Please ignore the branch name, I got my JIRA Ids mixed up 😅)

Brief change log

  • Introduced TablePipeline descriptor.
  • Introduced the ObjectIdentifier catalog entity.
  • Adds StatementSet.add to add a TablePipeline to the StatementSet.
  • Adds Table.insert_into to declare a TablePipeline with a given table path or table descriptor.

Verifying this change

This change is already covered by existing tests, such as (please describe tests):

  • Catalog and Table API completeness tests

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, functions added to Table and StatementSet)
  • 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)

@flinkbot
Copy link
Collaborator

flinkbot commented Feb 17, 2025

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@autophagy autophagy changed the title [FLINK-26089][python] Introduce TablePipeline descriptor to Python Table API [FLINK-37336][python] Introduce TablePipeline descriptor to Python Table API Feb 17, 2025
@autophagy
Copy link
Contributor Author

Closing this to reopen it with the correct Jira ticket ID - it isnt showing in Jira because of my initial mistake.

@autophagy autophagy closed this Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants