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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
