Thanks all for the votes.
So far, we have
- 3 binding +1 votes (Till, Andrey and Kurt)
- 2 un-binding +1 votes (Zhu and Xintong)
- No -1 votes
There are 3 binding +1 votes and no -1 votes, and the voting time has past.
According to the community bylaws, I'm glad to announce that FLIP-53
+1 from my side.
Thanks for bringing this up, Kurt. It's true that the accuracy loss of
floating values could cause problems in some cases. And I would consider
this as an implementation issue that can be discussed later in the PRs.
Thank you~
Xintong Song
On Sat, Sep 7, 2019 at 2:51 PM Kurt
+1 for FLIP-53.
I would like to raise one minor concern regarding to implementing
request absolute amount of memory case. Currently, it will be
translated to a memory fraction during compile, and translate back
to absolute value during execution. There is a risk that the user might
get less than h
Thanks for starting the vote @Xintong
+1 for the FLIP-53
Best,
Andrey
On Fri, Sep 6, 2019 at 3:53 PM Till Rohrmann wrote:
> Hi Xintong,
>
> thanks for starting this vote. The proposal looks good and, hence, +1 for
> it.
>
> One comment I have is concerning the first implementation step. I woul
Hi Xintong,
thanks for starting this vote. The proposal looks good and, hence, +1 for
it.
One comment I have is concerning the first implementation step. I would
suggest to not add the flag allSourcesInSamePipelinedRegion to the
ExecutionConfig because the ExecutionConfig is public API. Ideally w
Thanks Xintong for proposing this better resource management.
This helps a lot to users who want to better manage the job resources. And
would be even more useful if in the future we can have auto-tuning
mechanism for jobs.
+1 (non-binding)
Thanks,
Zhu Zhu
Xintong Song 于2019年9月6日周五 上午11:17写道：
