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

ASF GitHub Bot commented on FLINK-377:
--------------------------------------

Github user zentol commented on the pull request:

    https://github.com/apache/flink/pull/202#issuecomment-71611872
  
    Tests run on travis (they don't right now because fabian merged something 
that changes the CSVInputFormat constructor, which breaks stuff on my end) but 
see: 
    https://travis-ci.org/zentol/incubator-flink/jobs/48334902
    and search for "Running 
org.apache.flink.languagebinding.api.java.python.PythonPlanBinderTest"
    
    putting it under flink-python means splitting it from the generic 
interface, right? that would be necessary in the long run anyway, so I'm all 
for it.
    
    @dan-blanchard the generic interface is not just for python. it does reduce 
the amount of code you have to write in java by a pretty high amount. but It 
sets up some requirements, most prominently example support for binary data, 
memory-mapped files and sockets, though it would be possible to provide 
different options here. It is difficult for me to assess how difficult it would 
be; the generic and python part were coded and evolved simultaneously, and when 
something didn't fit i could just change it to do so. I think it's very likely 
that when someone wants to add another language we'll have to revisit a few 
things, but it provides at a good starting point.
    



> Create a general purpose framework for language bindings
> --------------------------------------------------------
>
>                 Key: FLINK-377
>                 URL: https://issues.apache.org/jira/browse/FLINK-377
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: GitHub Import
>              Labels: github-import
>             Fix For: pre-apache
>
>
> A general purpose API to run operators with arbitrary binaries. 
> This will allow to run Stratosphere programs written in Python, JavaScript, 
> Ruby, Go or whatever you like. 
> We suggest using Google Protocol Buffers for data serialization. This is the 
> list of languages that currently support ProtoBuf: 
> https://code.google.com/p/protobuf/wiki/ThirdPartyAddOns 
> Very early prototype with python: 
> https://github.com/rmetzger/scratch/tree/learn-protobuf (basically testing 
> protobuf)
> For Ruby: https://github.com/infochimps-labs/wukong
> Two new students working at Stratosphere (@skunert and @filiphaase) are 
> working on this.
> The reference binding language will be for Python, but other bindings are 
> very welcome.
> The best name for this so far is "stratosphere-lang-bindings".
> I created this issue to track the progress (and give everybody a chance to 
> comment on this)
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/377
> Created by: [rmetzger|https://github.com/rmetzger]
> Labels: enhancement, 
> Assignee: [filiphaase|https://github.com/filiphaase]
> Created at: Tue Jan 07 19:47:20 CET 2014
> State: open



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

Reply via email to