shuai.xu created FLINK-15964:
Summary: Getting previous stage in notFollowedBy may throw
exception
Key: FLINK-15964
URL: https://issues.apache.org/jira/browse/FLINK-15964
Project: Flink
Issue
Hi all,
I wanted to resurrect the thread about introducing a Java Expression
DSL. Please see the updated flip page[1]. Most of the flip was concluded
in previous discussion thread. The major changes since then are:
* accepting java.lang.Object in the Java DSL
* adding $ interpolation for a
zhijiang created FLINK-15963:
Summary: Reuse the same ByteBuf while writing the BufferResponse
header
Key: FLINK-15963
URL: https://issues.apache.org/jira/browse/FLINK-15963
Project: Flink
+1 (non-binding) for rc3
- build source successfully (inlcude test)
- ran e2e test locally
- test pojo serializer upgrade manually by running flink job.
Best,
Congxian
Zhu Zhu 于2020年2月10日周一 下午12:28写道：
> My bad. The missing commit info is caused by building from the src code zip
> which does
Hi everyone,
Thanks a lot for your feedback. I have created the FLIP[1].
Best,
Hequn
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP+96%3A+Support+Python+ML+Pipeline+API
On Mon, Feb 10, 2020 at 12:29 PM Dian Fu wrote:
> Hi Hequn,
>
> Thanks for bringing up the discussion. +1 to
Hi All,
Since we're about to release 1.10.0 (the vote of RC3 [1] is in good shape
although still not concluded), we plan to change fix version of the
unresolved issues to 1.11.0/1.10.1. We will start from issues with "Open"
status, and then the "In-Progress" ones. Any concerns, please let us
Thanks Dian for your reply.
+1 to create a FLIP too.
About "python.fn-execution.bundle.size" and
"python.fn-execution.arrow.batch.size", I got what are you mean about
"pipeline". I agree.
It seems that a batch should always in a bundle. Bundle size should always
bigger than batch size. (if a
Hi Hequn,
Thanks for bringing up the discussion. +1 to this feature. The design LGTM.
It's great that the Python ML users could use both the Java Pipeline
Transformer/Estimator/Model classes and the Python
Pipeline Transformer/Estimator/Model in the same job.
Regards,
Dian
On Mon, Feb 10, 2020
My bad. The missing commit info is caused by building from the src code zip
which does not contain the git info.
So this is not a problem.
+1 (binding) for rc3
Here's what's were verified :
* built successfully from the source code
* run a sample streaming and a batch job with parallelism=1000
Hi Dian,
Thanks a lot for bringing up the discussion!
It is great to see the Pandas UDFs feature is going to be introduced. I
think this would improve the performance and also the usability of
user-defined functions (UDFs) in Python.
One little suggestion: maybe it would be nice if we can add
Hi Rong,
Thanks a lot for joining the discussion!
It would be great if we can have a long term plan. My intention is to
provide a way for users to add dependencies of Flink ML, either through the
opt or download page. This would be more and more critical along with the
improvement of the Flink
Thanks everyone,
The vote has passed. The result is following:
+1 (Binding): 4, Kurt, Jark, Bowen, Timo.
+1 (Non-Binding): 3, Leonard, Zhenghua, Benchao.
Best,
Jingsong Lee
On Mon, Feb 10, 2020 at 10:12 AM Benchao Li wrote:
> +1 (non-binding). This is really helpful, thanks Jingsong for
Hi Dian,
Thanks for bring up this discussion. This is very important for the
ecological of PyFlink. Add support Pandas greatly enriches the available
UDF library of PyFlink and greatly improves the usability of PyFlink!
+1 for Support scalar vectorized Python UDF.
I think we should to create a
Hi Hequn,
Thanks for bring up this discussion.
+1 for add Python ML Pipeline API, even though the Java pipeline API may
change.
I would like to suggest create a FLIP for this API changes. :)
Best,
Jincheng
Hequn Cheng 于2020年2月5日周三 下午5:24写道：
> Hi everyone,
>
> FLIP-39[1] rebuilds the Flink
Hi there,
I am just exploring the apache flink git repo and found the performance test. I
have already test on my local machine, I’m wondering if we got online result?
Thanks
Regards
Xu Yan
+1 to make flink-docker repository self-contained, including the document.
And others refer
to it.
Best,
Yang
Till Rohrmann 于2020年2月9日周日 下午5:35写道：
> Sounds good to me Patrick. +1 for these changes.
>
> Cheers,
> Till
>
> On Fri, Feb 7, 2020 at 3:25 PM Patrick Lucas
> wrote:
>
> > Hi all,
> >
Huang Xingbo created FLINK-15961:
Summary: Introduce Python Physical Correlate RelNodes which are
containers for Python Python TableFunction
Key: FLINK-15961
URL:
+1 (non-binding). This is really helpful, thanks Jingsong for driving this.
Zhenghua Gao 于2020年2月10日周一 上午9:47写道：
> +1 (non-binding). Thanks for driving this.
>
> *Best Regards,*
> *Zhenghua Gao*
>
>
> On Fri, Feb 7, 2020 at 5:05 PM Leonard Xu wrote:
>
> > +1(non-binding), nice design!
> >
+1 (non-binding). Thanks for driving this.
*Best Regards,*
*Zhenghua Gao*
On Fri, Feb 7, 2020 at 5:05 PM Leonard Xu wrote:
> +1(non-binding), nice design!
> after read full discussion mail list.
>
> Best,
> Leonard Xu
>
> > 在 2020年2月6日，23:12，Timo Walther 写道：
> >
> > +1
> >
> > On 06.02.20
Bowen Li created FLINK-15960:
Summary: support creating Hive tables, views, functions within
Flink
Key: FLINK-15960
URL: https://issues.apache.org/jira/browse/FLINK-15960
Project: Flink
Issue
Dear community,
happy to share this week's community update. Activity on the dev@ mailing
list has picked up quite a bit this week and more and more concrete design
proposals for Flink 1.11 are brought up for discussion. Besides that, Flink
1.10 and flink-shaded 10.0 are both close to being
The commit info is shown as on the web UI and in logs.
Not sure if it's a common issue or just happens to my build only.
Thanks,
Zhu Zhu
aihua li 于2020年2月9日周日 下午7:42写道：
> Yes, but the results you see in the Performance Code Speed Center [3] skip
> FLIP-49.
> The results of the default
Yes, but the results you see in the Performance Code Speed Center [3] skip
FLIP-49.
The results of the default configurations are overwritten by the latest
results.
> 2020年2月9日 下午5:29，Yu Li 写道：
>
> Thanks for the efforts Aihua! These could definitely improve our RC test
> coverage!
>
>
Hi Till
I got your point, will create sub FLIPs and votings according to the
FLIP-75 and previous discussion soon.
Till Rohrmann 于2020年2月9日周日 下午5:27写道：
> Hi Yadong,
>
> I think it would be fine to simply link to this discussion thread to keep
> the discussion history. Maybe an easier way would
Hi everyone,
Please review and vote on the release candidate #1 for the version 10.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
Sounds good to me Patrick. +1 for these changes.
Cheers,
Till
On Fri, Feb 7, 2020 at 3:25 PM Patrick Lucas wrote:
> Hi all,
>
> For FLINK-15831[1], I think the way to start is for the flink-docker
> repo[2] itself to sufficiently document the workflow for publishing new
> Dockerfiles, and then
Thanks for the efforts Aihua! These could definitely improve our RC test
coverage!
Just to confirm, that the stability tests were executed with the same test
suite for Alibaba production usage, and the e2e performance one was
executed with the test suite proposed in FLIP-83 [1] and FLINK-14917
Hi Yadong,
I think it would be fine to simply link to this discussion thread to keep
the discussion history. Maybe an easier way would be to create top-level
FLIPs for the individual changes proposed in FLIP-75. The reason I'm
proposing this is that it would be easier to vote on it and to
28 matches
Mail list logo
