@Xingtong
I already know the modification of some api, but because there are many changes
involved,
I am afraid that the consideration is not comprehensive.
I'm willing to do the work, but I haven't found a committer yet.
Best,
Zhiqiang
发件人: Xintong Song
日期: 星期四, 2023年7月13日 10:03
收件人:
Thanks for the inputs, Zhiqiang and Jiabao.
@Zhiqiang,
The proposal sounds interesting. Do you already have an idea what API
changes are needed in order to make the connectors pluggable? I think
whether this should go into Flink 2.0 would significantly depend on what
API changes are needed.
Hi Yunfeng,
Thanks for the proposal. It makes sense to offer the optimization. I got
some NIT questions.
1. I guess you changed your thoughts while coding the POC, I found
pipeline.enable-operator-timestamp in the code but is
pipeline.force-timestamp-support defined in the FLIP
2. about the
Thanks for driving this Deepthi.
Looks great to me; a huge improvement over the current website. We had
agreed in the previous discussion [1] to keep the main website separate
from the docs since the target audience is different. I am inclined to
decouple the two and re-evaluate updating the docs
Thanks Xintong for driving the effort.
I’d add a +1 to improving out-of-box user experience, as suggested by @Jark and
@Chesnay.
For beginners, understanding complex configurations is a hard work.
In addition, the deployment of a set of Flink runtime environment is also a
complex matter.
At
Zili Chen created FLINK-32585:
-
Summary: Filter javax.xml.bind:jaxb-api false positive for Pulsar
connector
Key: FLINK-32585
URL: https://issues.apache.org/jira/browse/FLINK-32585
Project: Flink
Hi all,
I'm going on vacation tonight for 3 weeks.
Even if the vote is not finished, as the implementation is rather quick
and the design discussion had settled, I preferred I implementing
FLIP-322 [1] to allow people to take a look while I'm off.
[1]
Dawid Wysakowicz created FLINK-32584:
Summary: Make it possible to unset default catalog and/or database
Key: FLINK-32584
URL: https://issues.apache.org/jira/browse/FLINK-32584
Project: Flink
I have seen in [1] connectors and formats, and user code will be pluggable.
If the connectors are pluggable, the benefits are obvious, as the conflicts
between different jar package versions can be avoided.
If you don't use classloader isolation, shade is needed to resolve
conflicts. A lot of
Patrick Lucas created FLINK-32583:
-
Summary: RestClient can deadlock if request made after Netty event
executor terminated
Key: FLINK-32583
URL: https://issues.apache.org/jira/browse/FLINK-32583
Hi Dong,
Thanks for your reply!
Best regards,
Jing
On Wed, Jul 12, 2023 at 3:25 AM Dong Lin wrote:
> Hi Jing,
>
> Thanks for the comments. Please see my reply inline.
>
> On Wed, Jul 12, 2023 at 5:04 AM Jing Ge
> wrote:
>
> > Hi Dong,
> >
> > Thanks for the clarification. Now it is clear for
Hi all,
Would you mind casting your vote to this second vote thread (opened
after new discussions) so that the subject can move forward ?
@David, @Chesnay, @Robert you took part to the discussions, can you
please sent your vote ?
Thank you very much
Best
Etienne
Le 06/07/2023 à 13:02,
Matthias Pohl created FLINK-32582:
-
Summary: Move TypeSerializerUpgradeTestBase from Kafka connector
into flink-connector-common
Key: FLINK-32582
URL: https://issues.apache.org/jira/browse/FLINK-32582
Thanks Xintong for clarification. A guideline to help users migrating from
DataSet to DataStream will definitely be helpful.
Best regards,
Yuxia
- 原始邮件 -
发件人: "Xintong Song"
收件人: "dev"
发送时间: 星期三, 2023年 7 月 12日 上午 11:40:12
主题: Re: [VOTE] Release 2.0 must-have work items
@Yuxia,
We
14 matches
Mail list logo
