Hi, all. Currently, we use two seperated interfaces
SupportsComputedColumnPushDown and SupportsWatermarkPushDown in design. The
interface SupportsWatermarkPushDown relies on
SupportsComputedColumnPushDown when
watermark is defined on a computed column. During the implementation, we
find the meth
Thanks for starting this vote.
+1 from my side.
Thank you~
Xintong Song
On Fri, Sep 4, 2020 at 12:37 AM Till Rohrmann wrote:
> Hi devs,
>
> I'd like to start a voting thread on FLIP-138 [1], which proposes to make
> the slot protocol declarative. The proposal has been discussed in [2].
>
>
The new edits look good to me.
Looking forward to the vote.
Thanks,
Zhu
Xintong Song 于2020年9月4日周五 上午9:49写道：
> Thanks Till, the changes look good to me. Looking forward to the vote.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Fri, Sep 4, 2020 at 12:31 AM Till Rohrmann
> wrote:
>
> > Thanks for t
Hi all,
I would like to start the vote for FLIP-137[1], which is discussed and
reached a consensus in the discussion thread[2].
The vote will be open for at least 72h, unless there is an objection or not
enough votes.
Best,
Xingbo
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-137%3A
Huang Xingbo created FLINK-19138:
Summary: Python UDF supports directly specifying input_types as
DataTypes.ROW
Key: FLINK-19138
URL: https://issues.apache.org/jira/browse/FLINK-19138
Project: Flink
ABC created FLINK-19137:
---
Summary: Bump Apache Parquet to 1.11.1
Key: FLINK-19137
URL: https://issues.apache.org/jira/browse/FLINK-19137
Project: Flink
Issue Type: Improvement
Components: For
Dian Fu created FLINK-19136:
---
Summary: MetricsAvailabilityITCase.testReporter failed with "Could
not satisfy the predicate within the allowed time"
Key: FLINK-19136
URL: https://issues.apache.org/jira/browse/FLINK-19136
Thanks Till, the changes look good to me. Looking forward to the vote.
Thank you~
Xintong Song
On Fri, Sep 4, 2020 at 12:31 AM Till Rohrmann wrote:
> Thanks for the feedback Xintong and Zhu Zhu. I've added a bit more details
> for the intended interface extensions, potential follow ups (remo
Thanks Till, `taskmanager.memory.managed.consumer-weights` sounds good to
me.
Thank you~
Xintong Song
On Thu, Sep 3, 2020 at 8:44 PM Till Rohrmann wrote:
> Thanks for updating the FLIP Xintong. It looks good to me. One minor
> comment is that we could name the configuration parameter
> also
+1
>From the viewpoint of a developer, too many APIs also adds complexity and
risk
to the code change for job compilation stage and runtime stage.
Looking forward to the day that we can drop DataSet API and having a unified
one.
Thanks,
Zhu
David Anderson 于2020年9月4日周五 上午2:23写道：
> +1
>
>
> On T
+1
On Thu, Sep 3, 2020 at 3:06 PM Piotr Nowojski wrote:
> +1
>
> czw., 3 wrz 2020 o 10:08 Guowei Ma napisał(a):
>
> > +1
> > Looking forward to having a unified datastream api.
> > Best,
> > Guowei
> >
> >
> > On Thu, Sep 3, 2020 at 3:46 PM Dawid Wysakowicz
> > wrote:
> >
> > > +1
> > >
> > >
Aljoscha Krettek created FLINK-19135:
Summary: (Stream)ExecutionEnvironment.execute() should not throw
ExecutionException
Key: FLINK-19135
URL: https://issues.apache.org/jira/browse/FLINK-19135
Pr
Hi devs,
I'd like to start a voting thread on FLIP-138 [1], which proposes to make
the slot protocol declarative. The proposal has been discussed in [2].
The vote will be open for at least 72h + weekends. Hence, it can be closed
on September 9, unless there is an objection or not enough votes.
[
Thanks for the feedback Xintong and Zhu Zhu. I've added a bit more details
for the intended interface extensions, potential follow ups (removing the
AllocationIDs) and the question about whether to reuse or return a slot if
the profiles don't fully match.
If nobody objects, then I would start a vo
Hi Robert,
I haven’t tried yet with 1.11, on my list.
I’ll be spending time on this tomorrow, so hopefully more results.
As for setting the algorithm version 2, I do it in code like this:
Job job = Job.getInstance();
job.getConfiguration().set("io.serializations",
"cascading.tu
+1
czw., 3 wrz 2020 o 10:08 Guowei Ma napisał(a):
> +1
> Looking forward to having a unified datastream api.
> Best,
> Guowei
>
>
> On Thu, Sep 3, 2020 at 3:46 PM Dawid Wysakowicz
> wrote:
>
> > +1
> >
> > I think it gives a clear idea why we should deprecate and eventually
> > remove the DataS
Shuiqiang Chen created FLINK-19134:
--
Summary: Fix the converter of array coder for Python DataStream
API.
Key: FLINK-19134
URL: https://issues.apache.org/jira/browse/FLINK-19134
Project: Flink
Hi Xintong,
thanks for starting the vote.
+1 for the proposal given that we find a proper name for the
different memory consumers (specifically the batch/RocksDB consumer) and
their corresponding weights.
Cheers,
Till
On Thu, Sep 3, 2020 at 12:43 PM Xintong Song wrote:
> Hi devs,
>
> I'd like
Thanks for updating the FLIP Xintong. It looks good to me. One minor
comment is that we could name the configuration parameter
also taskmanager.memory.managed.consumer-weights which might be a bit more
expressive what this option does.
Cheers,
Till
On Thu, Sep 3, 2020 at 12:44 PM Xintong Song wr
User has just reported another issue FLINK-19133 which I think should be
a blocker for the 1.11.2 release. I'll try to prepare a fix as soon as
possible.
On 03/09/2020 09:36, Zhu Zhu wrote:
> Thanks for the inputs!
> I have made FLINK-14942 and FLINK-18641 blockers for 1.11.2.
>
> And thanks a lot
Dawid Wysakowicz created FLINK-19133:
Summary: User provided partitioners are not initialized correctly
Key: FLINK-19133
URL: https://issues.apache.org/jira/browse/FLINK-19133
Project: Flink
Hi community,
And by the way, during *FlinkKafkaProducer#initProducer*, the
*flinkKafkaPartitioner* is only opened when is is NOT null, which is
unfortunately not the case here, because it would be set to null if
*KafkaSerializationSchemaWrapper
*is provided in the arguments of the constructor.
[
Hi community,
We have found a serious issue with the newly-introduced
*KafkaSerializationSchemaWrapper
*class, which eventually let *FlinkKafkaProducer *only write to partition 0
in the given Kafka topic under certain conditions.
First let's look at this constructor in the universal version of
*F
Hi everyone,
Are there more comments about this FLIP? If not, I would like to bring up the
VOTE.
Best,
Wei
> 在 2020年9月1日，11:15，Wei Zhong 写道：
>
> Hi Timo,
>
> Thanks for your notification. I’ll remove it from the design doc.
>
> Best,
> Wei
>
>> 在 2020年8月31日，21:11，Timo Walther 写道：
>>
>> H
Hi Danny,
"if ChangelogMode.INSERT is the default, existing pipelines should be
compatible"
It is not about changelog mode compatibility, it is about the type
compatibility. The renaming to `toInsertStream` is only to have a mean
of dealing with data type inconsistencies that could break exi
Olivier Zembri created FLINK-19132:
--
Summary: Failed to start jobs for consuming Secure Kafka after
cluster restart
Key: FLINK-19132
URL: https://issues.apache.org/jira/browse/FLINK-19132
Project: Fl
Hi everyone,
Thanks all of you for the discussion.
If there are no objections, I would like to start a vote thread tomorrow.
Best,
Xingbo
Dian Fu 于2020年9月3日周四 下午5:45写道：
> Thanks for preparing the FLIP, xingbo!
>
> LGTM overall and looking forward to the voting!
>
> Regards,
> Dian
>
> > 在 2020
Thanks all for the feedback.
FYI, I've opened a voting thread[1] on this.
Thank you~
Xintong Song
[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-FLIP-141-Intra-Slot-Managed-Memory-Sharing-td44358.html
On Thu, Sep 3, 2020 at 2:54 PM Zhu Zhu wrote:
> Thanks for propo
Hi devs,
I'd like to start a voting thread on FLIP-141[1], which proposes how
managed memory should be shared by various use cases within a slot. The
proposal has been discussed in [2].
The vote will be open for at least 72h + weekends. I'll try to close it on
September 8, unless there is an obje
Thanks for preparing the FLIP, xingbo!
LGTM overall and looking forward to the voting!
Regards,
Dian
> 在 2020年9月3日，下午5:22，jincheng sun 写道：
>
> Thank you! looking forward to the voting :)
>
> Best,
> Jincheng
>
>
> Xingbo Huang 于2020年9月3日周四 下午2:39写道：
>
>> Hi Jincheng,
>>
>> Yes, I agree t
"It is a more conservative approach to introduce that in a
new method rather than changing the existing one under the hood and
potentially break existing pipelines silently”
I like the idea actually, but if ChangelogMode.INSERT is the default, existing
pipelines should be compatible. We can see t
Thank you! looking forward to the voting :)
Best,
Jincheng
Xingbo Huang 于2020年9月3日周四 下午2:39写道：
> Hi Jincheng,
>
> Yes, I agree that users can extend the class `AggregateFunction` if they
> want to define a Pandas UDAF by the way of custom classes. I have updated
> the part of the FLIP.
>
> Bes
sunjincheng created FLINK-19131:
---
Summary: Add py38 support in PyFlink
Key: FLINK-19131
URL: https://issues.apache.org/jira/browse/FLINK-19131
Project: Flink
Issue Type: New Feature
C
+1
Looking forward to having a unified datastream api.
Best,
Guowei
On Thu, Sep 3, 2020 at 3:46 PM Dawid Wysakowicz
wrote:
> +1
>
> I think it gives a clear idea why we should deprecate and eventually
> remove the DataSet API.
>
> Best,
>
> Dawid
>
> On 03/09/2020 09:37, Yun Gao wrote:
> > Very
+1
I think it gives a clear idea why we should deprecate and eventually
remove the DataSet API.
Best,
Dawid
On 03/09/2020 09:37, Yun Gao wrote:
> Very thanks for bring this up! +1 for deprecating the DataSet API and
> providing a unified streaming/batch programming model to users.
>
> Best,
Very thanks for bring this up! +1 for deprecating the DataSet API and
providing a unified streaming/batch programming model to users.
Best,
Yun
--
Sender:Aljoscha Krettek
Date:2020/09/02 19:22:51
Recipient:Flink Dev
Theme:[VOTE]
Thanks for the inputs!
I have made FLINK-14942 and FLINK-18641 blockers for 1.11.2.
And thanks a lot for offering help, zhijiang!
Thanks,
Zhu
Congxian Qiu 于2020年9月3日周四 下午3:18写道：
> Hi
> I'd like to include FLINK-14942 into 1.11.2. FLINK-14942 (this fixes a
> bug introduce in 1.11.0), there
Hi
I'd like to include FLINK-14942 into 1.11.2. FLINK-14942 (this fixes a
bug introduce in 1.11.0), there is a pr for it already.
Best,
Congxian
Zhou, Brian 于2020年9月3日周四 上午11:21写道：
> Hi,
>
> Thanks Becket for addressing the issue. FLINK-18641 is now a blocker for
> Pravega connector integra
Thanks for the nice summary Dawid. I also see the pain points in this
part of the API. Most of the users just want to add a time attribute.
I'm not sure how much projection features we need to have in a
`fromDataStream`. Users can do column renaming/reordering afterwards in
a `.select()`.
The
39 matches
Mail list logo
