WilliamSong112 opened a new pull request #16014:
URL: https://github.com/apache/flink/pull/16014


   > ## What is the purpose of the change
   > Add documentation of TableResult.collect for Python Table API
   > 
   > ## Brief change log
   > Add documentation of TableResult.collect for Python Table API
   > 
   > ## Verifying this change
   > _(Please pick either of the following options)_
   > 
   > This change is a trivial rework / code cleanup without any test coverage.
   > 
   > _(or)_
   > 
   > This change is already covered by existing tests, such as _(please 
describe tests)_.
   > 
   > _(or)_
   > 
   > This change added tests and can be verified as follows:
   > 
   > _(example:)_
   > 
   > * _Added integration tests for end-to-end deployment with large payloads 
(100MB)_
   > * _Extended integration test for recovery after master (JobManager) 
failure_
   > * _Added test that validates that TaskInfo is transferred only once across 
recoveries_
   > * _Manually verified the change by running a 4 node cluser with 2 
JobManagers and 4 TaskManagers, a stateful streaming program, and killing one 
JobManager and two TaskManagers during the execution, verifying that recovery 
happens correctly._
   > 
   > ## 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)`:  no
   > * 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/Mesos, ZooKeeper:  no
   > * The S3 file system connector: no
   > 
   > ## Documentation
   > * Does this pull request introduce a new feature? no
   > * If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented)


-- 
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:
us...@infra.apache.org


Reply via email to