lindong28 opened a new pull request #4:
URL: https://github.com/apache/flink-ml/pull/4


   ## What is the purpose of the change
   
   This PR updates the Flink ML API according to 
[FLIP-173](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=184615783).
   
   ## Brief change log
   
   This PR mades the following changes:
   - Added the AlgoOperator class. AlgoOperator class has the same interface as 
the existing Transformer (i.e. provides the transform(...) API).
   - Updated fit/transform methods to take list of tables as inputs and return 
list of tables as output.
   - Added setModelData and getModelData to the Model interface.
   - Removed the methods PipelineStage::toJson and PipelineStage::loadJson. 
Added methods save(...) and load(...) to the Stage interface.
   - Removed TableEnvironment from the parameter list of fit/transform APIs.
   - Added pipelineModel and let Pipeline implement only the Estimator. 
Pipeline is no longer a Transformer.
   - Removed Pipeline::appendStage from the Pipeline class.
   - Renamed PipelineStage to Stage and add the PublicEvolving tag to the Stage 
interface.
   
   ## Verifying this change
   
   This PR focuses on changing the Flink ML API. Some APIs such as save/load 
needs to be implemented after we complete the design of the parameter interface.
   
   We will have followup PRs to implement all the Flink ML APIs and provide 
better test coverage.
   
   ## 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)
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (yes)
   - If yes, how is the feature documented? (Java doc)


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to