Thanks for your confirm Till !
Publish the PyFlink into PyPI is very important for our user, I
have initiated a voting thread.
Best,
Jincheng
Till Rohrmann 于2019年7月29日周一 下午3:01写道：
> Sounds good to me. Thanks for driving this discussion.
>
> Cheers,
> Till
>
> On Mon, Jul 29, 2019 at 9:24 AM ji
Sounds good to me. Thanks for driving this discussion.
Cheers,
Till
On Mon, Jul 29, 2019 at 9:24 AM jincheng sun
wrote:
> Yes Till, I think you are correct that we should make sure that the
> published Flink Python API cannot be arbitrarily deleted.
>
> So, It seems that our current consensus i
Yes Till, I think you are correct that we should make sure that the
published Flink Python API cannot be arbitrarily deleted.
So, It seems that our current consensus is:
1. Should we re publish the PyFlink into PyPI --> YES
2. PyPI Project Name ---> apache-flink
3. How to handle Scala_2.11 and Sc
Sorry for chiming in so late. I would be in favor of option #2.
I guess that the PMC would need to give the credentials to the release
manager for option #1. Hence, the PMC could also add the release manager as
a maintainer which makes sure that only the PMC can delete artifacts.
Cheers,
Till
On
Hi all,
Thanks for all of your reply!
Hi Stephan, thanks for the reply and prove the details we need to pay
attention to. such as: Readme and Trademark compliance. Regarding the PyPI
account for release, #1 may have some risk that our release package can be
deleted by anyone who know the passwor
if we ship a binary, we should ship the binary we usually ship, not some
highly customized version.
On 24/07/2019 05:19, Dian Fu wrote:
Hi Stephan & Jeff,
Thanks a lot for sharing your thoughts!
Regarding the bundled jars, currently only the jars in the flink binary
distribution is packaged
Hi Stephan & Jeff,
Thanks a lot for sharing your thoughts!
Regarding the bundled jars, currently only the jars in the flink binary
distribution is packaged in the pyflink package. That maybe a good idea to also
bundle the other jars such as flink-hadoop-compatibility. We may need also
consider
+1 for publishing pyflink to pypi.
Regarding including jar, I just want to make sure which flink binary
distribution we would ship with pyflink since we have multiple flink binary
distributions (w/o hadoop).
Personally, I prefer to use the hadoop-included binary distribution.
And I just want to c
Hi!
Sorry for the late involvement. Here are some thoughts from my side:
Definitely +1 to publishing to PyPy, even if it is a binary release.
Community growth into other communities is great, and if this is the
natural way to reach developers in the Python community, let's do it. This
is not abou
Hi All,
Thanks for the feedback @Chesnay Schepler @Dian!
I think using `apache-flink` for the project name also makes sense to me.
due to we should always keep in mind that Flink is owned by Apache. (And
beam also using this pattern `apache-beam` for Python API)
Regarding the Python API release
So this would not be a source release then, but a full-blown binary release.
Maybe it is just me, but I find it a bit suspect to ship an entire java
application via PyPI, just because there's a Python API for it.
We definitely need input from more people here.
On 03/07/2019 14:09, Dian Fu wro
Hi Chesnay,
Thanks a lot for the suggestions.
Regarding “distributing java/scala code to PyPI”:
The Python Table API is just a wrapper of the Java Table API and without the
java/scala code, two steps will be needed to set up an environment to execute a
Python Table API program:
1) Install pyfli
The existing artifact in the pyflink project was neither released by the
Flink project / anyone affiliated with it nor approved by the Flink PMC.
As such, if we were to use this account I believe we should delete it to
not mislead users that this is in any way an apache-provided
distribution.
Hi all,
With the effort of FLIP-38 [1], the Python Table API(without UDF support
for now) will be supported in the coming release-1.9.
As described in "Build PyFlink"[2], if users want to use the Python Table
API, they can manually install it using the command:
"cd flink-python && python3 setup.py
14 matches
Mail list logo
