SteNicholas opened a new pull request #12770:
URL: https://github.com/apache/flink/pull/12770

   ## What is the purpose of the change
   
   *Currently, there are a few deprecated interfaces which are still heavily 
used in the tests and examples, e.g. register_function, etc. Deprecated 
interfaces should be replaced to improve the tests and examples to use the new 
interfaces, such as create_temporary_system_function instead.*
   
   ## Brief change log
   
     - *Modity tests and examples including calling method `insert_into`, 
`scan`, `sql_update`, `register_function`, `register_java_function` of 
`TableEnvironment`.*
     - *Modity tests and examples including calling method `insert_into` of 
`Table`.*
     - *Deprecate method `from_table_source`, `_from_elements`, `connect` of 
`TableEnvironment`.*
   
   ## Verifying this change
   
     - *Modity unit tests including calling method `insert_into`, `scan`, 
`sql_update`, `register_function`, `register_java_function` of 
`TableEnvironment`.*
     - *Modity unit tests including calling method `insert_into` of `Table`.*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / 
don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **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