[ 
https://issues.apache.org/jira/browse/FLINK-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328882#comment-14328882
 ] 

Paris Carbone commented on FLINK-1421:
--------------------------------------

Thanks for all the great feedback everyone! I believe the adapter is ready for 
a PR! :)
The current Flink-Samoa adapter runs well for all existing Tasks in local and 
remote mode. The only external requirement, at least from the samoa executable 
script is to have the Flink CLI and its dependencies installed and exported 
into a FLINK_HOME variable.

[~StephanEwen] We should address the proper serialisation in the next patch.

[~azaroth] We have rebased our current branch [1] with the incubator-samoa 
repository master and we also created a JIRA for the PR [2]. Do you think it is 
ok to do the PR now or should we wait for some upcoming refactoring that 
affects the adapters?

[1] https://github.com/senorcarbone/samoa/tree/flink-integration
[2] https://issues.apache.org/jira/browse/SAMOA-16

> Implement a SAMOA Adapter for Flink Streaming
> ---------------------------------------------
>
>                 Key: FLINK-1421
>                 URL: https://issues.apache.org/jira/browse/FLINK-1421
>             Project: Flink
>          Issue Type: New Feature
>          Components: Streaming
>            Reporter: Paris Carbone
>            Assignee: Paris Carbone
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Yahoo's Samoa is an experimental incremental machine learning library that 
> builds on an abstract compositional data streaming model to write streaming 
> algorithms. The task is to provide an adapter from SAMOA topologies to 
> Flink-streaming job graphs in order to support Flink as a backend engine for 
> SAMOA tasks.
> A statup guide can be viewed here :
> https://docs.google.com/document/d/18glDJDYmnFGT1UGtZimaxZpGeeg1Ch14NgDoymhPk2A/pub
> The main working branch of the adapter :
> https://github.com/senorcarbone/samoa/tree/flink-integration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to