Hello,
I would say no, as the general reception of the Python API was
*tumbleweed* so far.
In my opinion this would just lead to a massive increase in code to
maintain; we would need at least 2-3 active long-term python contributors.
Especially so since ML, CEP and Table are afaik still in heavy development.
If anything, before thinking about porting the libraries to python it
would make more sense to implement a python streaming API.
Or maybe /finish/ porting the DataSet API...
Regards,
Chesnay
On 19.08.2016 22:07, Ivan Mushketyk wrote:
Hi Flink developers,
It seems to me that Flink has two important "selling points":
1. It has Java, Scala and Python APIs
2. I has a number of useful libraries (ML, Gelly, CEP, and Table)
But as far as I understand, currently users cannot use any of these
libraries using a Python API. It seems to be a gap worth filling.
What do you think about it? Does it make sense to add CEP/Gelly/ML/Table
Python APIs?
Best regards,
Ivan.
