I would just remove them. As you said, there are very limited as to what
features they support, and haven't been under active development for
several releases.
Existing users (if there even are any) could continue to use older
version against newer releases. It's is slightly more involved than for
say, flink-ml, as you also have to copy the start-scripts (or figure out
how to use the jars yourself), but it is still feasible and can be
documented in the release notes.
On 11/06/2019 15:30, Stephan Ewen wrote:
Hi all!
I would suggest to deprecating the existing python APIs for DataSet and
DataStream API with the 1.9 release.
Background is that there is a new Python API under development.
The new Python API is initially against the Table API. Flink 1.9 will
support Table API programs without UDFs, 1.10 is planned to support UDFs.
Future versions would support also the DataStream API.
In the long term, Flink should have one Python API for DataStream and Table
APIs. We should not maintain multiple different implementations and confuse
users that way.
Given that the existing Python APIs are a bit limited and not under active
development, I would suggest to deprecate them in favor of the new API.
Best,
Stephan
