Hi folks,
The bug has been fixed and PR at docker-library/official-images has been
merged. The official images are available now.
Best regards,
Jing
On Mon, Jan 22, 2024 at 11:39 AM Jing Ge wrote:
> Hi folks,
>
> I am still working on the official images because of the issu
Hi folks,
The bug has been fixed and PR at docker-library/official-images has been
merged. The official images are available now.
Best regards,
Jing
On Mon, Jan 22, 2024 at 11:39 AM Jing Ge wrote:
> Hi folks,
>
> I am still working on the official images because of the issu
Hi folks,
I am still working on the official images because of the issue
https://issues.apache.org/jira/browse/FLINK-34165. Images under
apache/flink are
available.
Best regards,
Jing
On Sun, Jan 21, 2024 at 11:06 PM Jing Ge wrote:
> Thanks Leonard for the feedback! Also thanks @Jark
Hi folks,
I am still working on the official images because of the issue
https://issues.apache.org/jira/browse/FLINK-34165. Images under
apache/flink are
available.
Best regards,
Jing
On Sun, Jan 21, 2024 at 11:06 PM Jing Ge wrote:
> Thanks Leonard for the feedback! Also thanks @Jark
t; Thanks all who involved this release!
>
> Best,
> Leonard
>
> > 2024年1月20日 上午12:01，Jing Ge 写道：
> >
> > The Apache Flink community is very happy to announce the release of
> Apache
> > Flink 1.18.1, which is the first bugfix release for the Apache Flink 1
t; Thanks all who involved this release!
>
> Best,
> Leonard
>
> > 2024年1月20日 上午12:01，Jing Ge 写道：
> >
> > The Apache Flink community is very happy to announce the release of
> Apache
> > Flink 1.18.1, which is the first bugfix release for the Apache Flink 1
The Apache Flink community is very happy to announce the release of Apache
Flink 1.18.1, which is the first bugfix release for the Apache Flink 1.18
series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
The Apache Flink community is very happy to announce the release of Apache
Flink 1.18.1, which is the first bugfix release for the Apache Flink 1.18
series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
any further thoughts.
>
> Best regards,
> Junrui
>
> Jing Ge 于2023年11月20日周一 05:46写道：
>
>> Hi Junrui,
>>
>> Thanks for bringing this to our attention. First of all, it makes sense
>> to deprecate RuntimeContext#getExecutionConfig.
>>
>> Afaic
Hi Junrui,
Thanks for bringing this to our attention. First of all, it makes sense to
deprecate RuntimeContext#getExecutionConfig.
Afaic, this is an issue of how we design API with clean concepts/aspects.
There are two issues mentioned in the FLIP:
1. short of user-facing abstraction - we just
The Apache Flink community is very happy to announce the release of Apache
Flink 1.18.0, which is the first release for the Apache Flink 1.18 series.
Apache Flink® is an open-source unified stream and batch data processing
framework for distributed, high-performing, always-available, and accurate
The Apache Flink community is very happy to announce the release of Apache
Flink 1.18.0, which is the first release for the Apache Flink 1.18 series.
Apache Flink® is an open-source unified stream and batch data processing
framework for distributed, high-performing, always-available, and accurate
快了，已经开始voting了 :-))
On Sun, Oct 15, 2023 at 5:55 AM kcz <573693...@qq.com.invalid> wrote:
>
also be patched by us).
>
>
>
> Kind regards,
>
> Christian
>
>
>
> *Von: *Jing Ge via user
> *Datum: *Dienstag, 22. August 2023 um 11:40
> *An: *liu ron
> *Cc: *user@flink.apache.org
> *Betreff: *Re: Flink 1.17.2 planned?
>
> This email has reached Mapp via
Hi devs,
Thanks Giannis for your suggestion. It seems that the last email wasn't
sent to the dev ML. It is also an interesting topic for devs and user-zh.
Best regards,
Jing
-- Forwarded message -
From: Giannis Polyzos
Date: Tue, Aug 22, 2023 at 11:11 AM
Subject: [Discussion]
Hi devs,
Thanks Giannis for your suggestion. It seems that the last email wasn't
sent to the dev ML. It is also an interesting topic for devs and user-zh.
Best regards,
Jing
-- Forwarded message -
From: Giannis Polyzos
Date: Tue, Aug 22, 2023 at 11:11 AM
Subject: [Discussion]
Hi Christian,
Thanks for reaching out. Liked Ron pointed out that the community is
focusing on the 1.18 release. If you are facing urgent issues, would you
like to volunteer as the release manager of 1.17.2 and drive the release?
Theoretically, everyone could be the release manager of a bugs fix
Congratulations!
Best regards,
Jing
On Mon, Jul 3, 2023 at 3:21 PM yuxia wrote:
> Congratulations!
>
> Best regards,
> Yuxia
>
> --
> *发件人: *"Pushpa Ramakrishnan"
> *收件人: *"Xintong Song"
> *抄送: *"dev" , "User"
> *发送时间: *星期一, 2023年 7 月 03日 下午 8:36:30
> *主题: *Re:
ward to receiving your submission and welcoming you
as a speaker at the Flink Forward Conference.
Thank you for your time and consideration.
Best regards,
--
Jing Ge | Head of Engineering
j...@ververica.com
<https://www.ververica.com/>
Follow us @VervericaData
--
Join Flink Forw
Hi Chris,
not yet and we are working on it[1].
best regards,
Jing
[1]
https://issues.apache.org/jira/browse/FLINK-15736?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17697544#comment-17697544
On Thu, Jun 1, 2023 at 11:40 PM Joseph, Chris S
wrote:
> Hi,
>
>
>
> Does
Thanks Qingsheng for driving it!
@Devs
As you might already be aware of, there are many externalizations and new
releases of Flink connectors. Once a connector has been externalized
successfully, i.e. the related module has been removed in the Flink repo,
we will not set a priority higher than
est regards,
>
> Weijie
>
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
>
> [2] https://github.com/pypa/twine/issues/997
>
>
> Jing Ge 于2023年5月27日周六 00:15写道：
>
> > Hi Weijie,
> >
> > Thanks again for your effort. I w
est regards,
>
> Weijie
>
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
>
> [2] https://github.com/pypa/twine/issues/997
>
>
> Jing Ge 于2023年5月27日周六 00:15写道：
>
> > Hi Weijie,
> >
> > Thanks again for your effort. I w
Hi Weijie,
Thanks again for your effort. I was wondering if there were any obstacles
you had to overcome while releasing 1.16.2 and 1.17.1 that could lead us to
any improvement wrt the release process and management?
Best regards,
Jing
On Fri, May 26, 2023 at 4:41 PM Martijn Visser
wrote:
>
Hi Weijie,
Thanks again for your effort. I was wondering if there were any obstacles
you had to overcome while releasing 1.16.2 and 1.17.1 that could lead us to
any improvement wrt the release process and management?
Best regards,
Jing
On Fri, May 26, 2023 at 4:41 PM Martijn Visser
wrote:
>
Hi Weijie,
That is earlier than I expected! Thank you so much for your effort!
Best regards,
Jing
On Fri, May 26, 2023 at 4:44 PM Martijn Visser
wrote:
> Same here as with Flink 1.16.2, thank you Weijie and those who helped with
> testing!
>
> On Fri, May 26, 2023 at 1:08 PM weijie guo
>
Hi Weijie,
That is earlier than I expected! Thank you so much for your effort!
Best regards,
Jing
On Fri, May 26, 2023 at 4:44 PM Martijn Visser
wrote:
> Same here as with Flink 1.16.2, thank you Weijie and those who helped with
> testing!
>
> On Fri, May 26, 2023 at 1:08 PM weijie guo
>
cc user ML to get more attention, since the plugin will be used by Flink
application developers.
Best regards,
Jing
On Mon, May 22, 2023 at 3:32 PM Jing Ge wrote:
> Hi Emre,
>
> Thanks for clarifying it. Afaiac, it is a quite interesting proposal,
> especially for Flink job de
?
Best regards,
Jing
On Thu, Apr 27, 2023 at 8:18 AM Tamir Sagi
wrote:
> More details about the JDK bug here
> https://bugs.openjdk.org/browse/JDK-8277529
>
> Related Jira ticket
> https://issues.apache.org/jira/browse/FLINK-24998
>
> ------
> *From:* J
, 2023 at 11:10 AM tanjialiang wrote:
> Hi, Jing Ge
> 感谢你的回复。
> 目前我已经发起了一个英文的邮件讨论（大约两周前），但是目前回复邮件的开发者只有一个，针对这种情况我应该如何去安排后续的代码贡献工作？
>
>
> Best regrads,
> tanjialiang.
> ---- 回复的原邮件
> | 发件人 | Jing Ge |
> | 发送日期 | 2023年4月24日 16:30 |
> | 收件人 | |
> | 主题 | Re: 关于
Thanks Chesnay for working on this. Would you like to share more info about
the JDK bug?
Best regards,
Jing
On Mon, Apr 24, 2023 at 11:39 AM Chesnay Schepler
wrote:
> As it turns out Kryo isn't a blocker; we ran into a JDK bug.
>
> On 31/03/2023 08:57, Chesnay Schepler wrote:
>
>
>
Hi，
如果是增加public API变更的话，建议先发起一个英文的邮件讨论，然后看是否需要创建FLIP，然后在基于FLIP发起更具体的技术讨论
On Mon, Apr 24, 2023 at 10:06 AM tanjialiang wrote:
> Hello，everyone.
> 我想向apache
> flink贡献源码，由于修复这个issue需要新增一些API，按照流程需要发起邮件讨论，但这个topic只得到一名开发者关注，这样的情况下我应该如何进行后面的流程？期待有熟悉flink源码贡献的开发者可以提供帮助
>
>
> issue:
Dear devs and users,
Today was the kickoff meeting for Flink 1.18 release cycle. I'd like to
share the info synced in the meeting.
Meeting schedule:
Zoom will be used with a 40 mins limit for each meeting. That should be
fine for now. We will check it again if we have an issue with the time
Congrats!
Best regards,
Jing
On Mon, Mar 27, 2023 at 2:32 PM Leonard Xu wrote:
> Congratulations!
>
>
> Best,
> Leonard
>
> On Mar 27, 2023, at 5:23 PM, Yu Li wrote:
>
> Dear Flinkers,
>
>
>
> As you may have noticed, we are pleased to announce that Flink Table Store
> has joined the Apache
Congrats!
Best regards,
Jing
On Mon, Mar 27, 2023 at 2:32 PM Leonard Xu wrote:
> Congratulations!
>
>
> Best,
> Leonard
>
> On Mar 27, 2023, at 5:23 PM, Yu Li wrote:
>
> Dear Flinkers,
>
>
>
> As you may have noticed, we are pleased to announce that Flink Table Store
> has joined the Apache
Excellent work! Congratulations! Appreciate the hard work and contributions
of everyone in the Apache Flink community who helped make this release
possible. Looking forward to those new features. Cheers!
Best regards,
Jing
On Thu, Mar 23, 2023 at 10:24 AM Leonard Xu wrote:
> The Apache Flink
Excellent work! Congratulations! Appreciate the hard work and contributions
of everyone in the Apache Flink community who helped make this release
possible. Looking forward to those new features. Cheers!
Best regards,
Jing
On Thu, Mar 23, 2023 at 10:24 AM Leonard Xu wrote:
> The Apache Flink
3 at 8:17 AM Shammon FY wrote:
>
>> Hi jing,
>>
>> It sounds good to me, we can add an option for it
>>
>> Best,
>> Shammon
>>
>>
>> On Fri, Feb 17, 2023 at 3:13 PM Jing Ge wrote:
>>
>>> Hi,
>>>
>>> It makes sense t
Hi,
It makes sense to offer this feature of catching and ignoring exp with
config on/off, when we put ourselves in users' shoes. WDYT? I will create a
ticket if most of you consider it as a good feature to help users.
Best regards,
Jing
On Fri, Feb 17, 2023 at 6:01 AM Shammon FY wrote:
> Hi
Hi Yanfei,
Thanks for your effort. Looking forward to checking it.
Best regards,
Jing
On Mon, Jan 30, 2023 at 1:42 PM Yanfei Lei wrote:
> It is very happy to announce the release of FRocksDB 6.20.3-ververica-2.0.
>
> Compiled files for Linux x86, Linux arm, Linux ppc64le, MacOS x86,
> MacOS
Hi Yanfei,
Thanks for your effort. Looking forward to checking it.
Best regards,
Jing
On Mon, Jan 30, 2023 at 1:42 PM Yanfei Lei wrote:
> It is very happy to announce the release of FRocksDB 6.20.3-ververica-2.0.
>
> Compiled files for Linux x86, Linux arm, Linux ppc64le, MacOS x86,
> MacOS
>
>>
>> Do you know, if this problem will be addressed in FLINK-28867
>> <https://issues.apache.org/jira/browse/FLINK-28867> or it deserve a
>> separate Jira?
>>
>>
>>
>>
>>
>> *From: *Jing Ge
>> *Date: *Tues
Hi Michael,
Currently, ParquetColumnarRowInputFormat does not support schemas with
nested columns. If your parquet file stores Avro records. You might want to
try e.g. Avro Generic record[1].
[1]
Hi Etienne,
Nice blog! Thanks for sharing!
Best regards,
Jing
On Wed, Nov 9, 2022 at 5:49 PM Etienne Chauchot
wrote:
> Hi Yun Gao,
>
> FYI I just updated the article after your review:
> https://echauchot.blogspot.com/2022/11/flink-howto-migrate-real-life-batch.html
>
> Best
>
> Etienne
> Le
Congrats!
On Fri, Oct 28, 2022 at 1:22 PM 任庆盛 wrote:
> Congratulations and a big thanks to Chesnay, Martijn, Godfrey and Xingbo
> for the awesome work for 1.16!
>
> Best regards,
> Qingsheng Ren
>
> > On Oct 28, 2022, at 14:46, Xingbo Huang wrote:
> >
> > The Apache Flink community is very
Congrats!
On Fri, Oct 28, 2022 at 1:22 PM 任庆盛 wrote:
> Congratulations and a big thanks to Chesnay, Martijn, Godfrey and Xingbo
> for the awesome work for 1.16!
>
> Best regards,
> Qingsheng Ren
>
> > On Oct 28, 2022, at 14:46, Xingbo Huang wrote:
> >
> > The Apache Flink community is very
e IO. This needs time to design, discuss, adjust
> and vote, but considering this is blocking 1.16, maybe it’s better to
> rescue the compatibility for now, and leave the huge reconstruction to
> future versions (maybe 2.0).
>
> Best,
> Qingsheng
>
> On Wed, Oct 12, 2022 a
Hi Qingsheng,
Just want to make sure we are on the same page. Are you suggesting
switching the naming between "numXXXSend" and "numXXXOut" or reverting all
the changes we did with FLINK-26126 and FLINK-26492?
For the naming switch, please pay attention that the behaviour has been
changed since
Hi Martijn,
Thanks for bringing this up. It is generally a great idea, so +1.
Since both scala extension projects mentioned in the FLIP are still very
young and I don't think they will attract more scala developers as Flink
could just because they are external projects. It will be a big issue
Hi,
Welcome to the Flink community!
A DataStreamSource is a DataStream. It is normally used as the starting
point of a DataStream. All related methods in StreamExecutionEnvironment
that create a DataStream return actually a DataStreamSource, because it is
where a DataStream starts.
Commonly,
我理解，目前大的目标是为了流批一体，设计上实际上是对存储进行了抽象，从某种角度上来看可以理解为存储虚拟化，未来的想象空间要大很多。Iceberg，Hudi这些可以作为底层对接的一种具体实现。
On Fri, Sep 9, 2022 at 2:44 PM Xuyang wrote:
> Hi，我理解Flink table store主要有以下几个优势：
> 1、减少架构复杂性，不需要额外引入多余的组件
> 2、支持Flink计算中直接使用Flink table store的存储
> 3、毫秒级流式查询和olap能力
>
>
>
>
> --
>
> Best！
>
Hi,
I would recommend you to check the release notes of 1.14[1] and 1.15[2]. If
your Flink jobs are using Flink features that have big improvements in
these two releases, it would be better to upgrade step by step without
skipping 1.14.x.
In general, depending on how complicated your jobs are,
Thanks Danny for your effort!
Best regards,
Jing
On Wed, Aug 24, 2022 at 11:43 PM Danny Cranmer
wrote:
> The Apache Flink community is very happy to announce the release of Apache
> Flink 1.15.2, which is the second bugfix release for the Apache Flink 1.15
> series.
>
> Apache Flink® is an
Thanks Danny for your effort!
Best regards,
Jing
On Wed, Aug 24, 2022 at 11:43 PM Danny Cranmer
wrote:
> The Apache Flink community is very happy to announce the release of Apache
> Flink 1.15.2, which is the second bugfix release for the Apache Flink 1.15
> series.
>
> Apache Flink® is an
Congrats! Thank you all!
Best regards,
Jing
On Mon, Jul 25, 2022 at 7:51 AM Px New <15701181132mr@gmail.com> wrote:
>
>
> Yang Wang 于2022年7月25日周一 10:55写道：
>
> > Congrats! Thanks Gyula for driving this release, and thanks to all
> > contributors!
> >
> >
> > Best,
> > Yang
> >
> > Gyula
Hi,
using FLASH_SSD_OPTIMIZED already sets the number of threads to 4. This
optimization can improve the source throughput and reduce the delayed wrate
rate.
If this optimization didn't fix the back pressure, could you share more
information about your job? Could you check the metric of the back
Hi,
you don't have to do that. Next time you can try "Invalidate Caches..."
under the File menu in Intellij Idea.
Best regards,
Jing
On Wed, Jul 13, 2022 at 7:21 PM Min Tu via user
wrote:
> Thanks a lot !! I have removed the .idea folder and the unit test works.
>
> On Mon, Jul 11, 2022 at
To: bastien dine
Cc: Martijn Visser , Jing Ge ,
user
请问这个邮件咋退订？
Replied Message
>From bastien dine
Date 06/15/2022 17:50
To Martijn Visser
Cc Jing Ge ,
user
Subject Re: New KafkaSource API : Change in default behavior regarding
starting offset
Hello Martijn,
Thanks for the l
f these
> components. We would ideally like to measure these:
> 1. Number of rows emitted by the source per unit time
> 2. Time taken by the enumerator to discover the splits
> 3. Total splits discovered
>
>
> Regards,
> Meghajit
>
>
> On Fri, Jun 10, 2022 at 10:04 PM Jing
Hi,
Just like Shengkai mentioned. I would strongly suggest trying SQL for ETL
dag. If you find anything that SQL does not work for you, please share your
requirements with us. We might check if it makes sense to build new
features in Flink to support them.
Best regards,
Jing
On Wed, Jun 15,
Hi Bastien,
Thanks for asking. I didn't find any call of setStartFromGroupOffsets() within
Flink in the master branch. Could you please point out the code that
committed offset is used as default?
W.r.t. the new KafkaSource, if OffsetsInitializer.committedOffsets()
is used, an exception will be
Hi,
Please be aware that SourceFunction will be deprecated soon[1]. It is
recommended to build a new source connector based on the new Source API
design by FLIP-27[2]. You might take the Kafka connector as the
reference implementation.
Best regards,
Jing
[1]
Hi,
友情提醒：开ticket以及以后在dev里讨论，记得用英语哈。
祝好
Jing
On Tue, Jun 14, 2022 at 3:23 PM Yun Tang wrote:
> Hi，育锋
>
> 我觉得你的分析应该是没问题的。可以创建一个ticket来修复该问题。另外，关于代码实现的具体讨论，建议在dev邮件列表讨论。
>
> 祝好
> 唐云
>
> From: 朱育锋
> Sent: Tuesday, June 14, 2022 19:33
> To:
Hi meghajit,
I think it makes sense to extend the current metrics. Could you list all
metrics you need? Thanks!
Best regards,
Jing
On Fri, Jun 10, 2022 at 5:06 PM Lijie Wang wrote:
> Hi Meghajit,
>
> As far as I know, currently, the FileSource does not have the metrics you
> need. You can
Hi Carlos,
You might want to join the discussion about FLIP-238[1] to share your
thoughts with us. Thanks!
Best regards,
Jing
[1] https://lists.apache.org/thread/7gjxto1rmkpff4kl54j8nlg5db2rqhkt
On Thu, Jun 9, 2022 at 2:13 PM Sanabria, Carlos <
carlos.sanab...@accenture.com> wrote:
> Thanks
Hi Alexey,
There is a thread[1] discussing this issue right now. It would be great if
you could share some thoughts about your experience. Thanks!
Best regards,
Jing
[1]https://lists.apache.org/thread/d6cwqw9b3105wcpdkwq7rr4s7x4ywqr9
On Wed, Jun 8, 2022 at 4:42 PM Alexey Trenikhun wrote:
>
Hi Xiao,
Just done, please check. Thanks!
Best regards,
Jing
On Mon, Jun 6, 2022 at 3:59 AM Xiao Ma wrote:
> Hi Jing,
>
> Could you please add me to the slack channel also?
>
> Thank you.
>
>
> Best,
> Mark Ma
>
> On Sun, Jun 5, 2022 at 9:57 PM Jing Ge wro
Hi Sri,
Flink is very well documented. You can find it under e.g.
https://nightlies.apache.org/flink/flink-docs-master/
Best regards,
Jing
On Mon, Jun 6, 2022 at 3:39 AM sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> Hi Flink Community,
>
> I want to go through flink source
Hi Raghunadh,
Just did, please check your email. Thanks!
Best regards,
Jing
On Mon, Jun 6, 2022 at 3:51 AM Raghunadh Nittala
wrote:
> Team, Kindly add me to the slack channel.
>
> Best Regards.
>
mail.com> wrote:
>
>> Hi Jing,
>>
>> Please add me kali.tumm...@gmail.com.
>>
>> Thanks
>> Sri
>>
>> On Sat, Jun 4, 2022 at 4:47 PM Jing Ge wrote:
>>
>>> Hi Santhosh,
>>>
>>> just invited you. Please check your
>>
>> Please add me kali.tumm...@gmail.com.
>>
>> Thanks
>> Sri
>>
>> On Sat, Jun 4, 2022 at 4:47 PM Jing Ge wrote:
>>
>>> Hi Santhosh,
>>>
>>> just invited you. Please check your email. Looking forward to knowing
>>&g
Hi Sri,
I have invited you, please check. Thanks!
Best regards,
Jing
On Sun, Jun 5, 2022 at 6:02 PM sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> Hi Jing,
>
> Please add me kali.tumm...@gmail.com.
>
> Thanks
> Sri
>
> On Sat, Jun 4, 2022 at 4
Amazing! Thanks Yang for driving this! Thanks all for your effort!
Best regards,
Jing
On Sun, Jun 5, 2022 at 11:30 AM tison wrote:
> Congrats! Thank you all for making this release happen.
>
> Best,
> tison.
>
>
> rui fan <1996fan...@gmail.com> 于2022年6月5日周日 17:19写道：
>
>> Thanks Yang for
Amazing! Thanks Yang for driving this! Thanks all for your effort!
Best regards,
Jing
On Sun, Jun 5, 2022 at 11:30 AM tison wrote:
> Congrats! Thank you all for making this release happen.
>
> Best,
> tison.
>
>
> rui fan <1996fan...@gmail.com> 于2022年6月5日周日 17:19写道：
>
>> Thanks Yang for
Hi,
Invites have been sent. Please check your emails. Thanks!
Regards,
JIng
On Sun, Jun 5, 2022 at 12:38 PM Jay Ghiya wrote:
> Request community to share invite link for me at ghiya6...@gmail.com and
> jay.gh...@ge.com
>
Hi Santhosh,
just invited you. Please check your email. Looking forward to knowing your
story! Thanks!
To anyone else who wants to join, please send an email to
user@flink.apache.org, you might have a better chance to get the invite.
Thanks.
Regards,
Jing
On Sat, Jun 4, 2022 at 10:37 PM
PM Yuan Mei wrote:
> Thanks, Xintong and Jark the great effort driving this, and everyone for
> making this possible.
>
> I've also Twittered this announcement on our Apache Flink Twitter account.
>
> Best
>
> Yuan
>
>
>
> On Fri, Jun 3, 2022 at 12:54 AM Jing G
Hi,
Currently, the Flink Scala API is not in a good shape. Would you like to
start from there?
Best regards,
Jing
On Fri, Jun 3, 2022 at 4:29 PM sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> Hi Folks,
>
> Is anyone hiring for Flink or Scala Akka contract corp to corp
Hi,
It seems like an evaluation with a small dataset. In this case, would you
like to share your data sample and code? In addition, have you tried KMeans
with the same dataset and got inconsistent results too?
Best regards,
Jing
On Fri, Jun 3, 2022 at 4:29 AM Natia Chachkhiani <
Thanks everyone for your effort!
Best regards,
Jing
On Thu, Jun 2, 2022 at 4:17 PM Martijn Visser
wrote:
> Thanks everyone for joining! It's good to see so many have joined in such
> a short time already. I've just refreshed the link which you can always
> find on the project website [1]
>
>
Thanks everyone for your effort!
Best regards,
Jing
On Thu, Jun 2, 2022 at 4:17 PM Martijn Visser
wrote:
> Thanks everyone for joining! It's good to see so many have joined in such
> a short time already. I've just refreshed the link which you can always
> find on the project website [1]
>
>
Hi Bariša,
Could you share the reason why your data processing pipeline should keep
running when one kafka source is down?
It seems like any one among the multiple kafka sources is optional for the
data processing logic, because any kafka source could be the one that is
down.
Best regards,
Jing
Hi,
yuxia has already pointed out the correct direction. The exact line for
using the savepoint path to resume the job from a savepoint is at line 1326
[1]
[1]
Hi,
Afaik, there are still a lot of unit tests depending on it. I don't think
we can drop it before dropping all of these unit tests.
Best regards,
Jing
On Tue, May 31, 2022 at 8:10 AM Yun Gao wrote:
> Hi Jun,
>
> I think the release notes should only include the issues that cause changes
>
Hi,
1. What are the general usage scenarios of GlobalCommitter?
- GlobalCommitter is used for creating and committing an aggregated
committable. It is part of a 2-phase-commit protocol. One use case is the
compaction of small files.
2. Why should GlobalCommitter be removed in the new version of
Hi,
1. What are the general usage scenarios of GlobalCommitter?
- GlobalCommitter is used for creating and committing an aggregated
committable. It is part of a 2-phase-commit protocol. One use case is the
compaction of small files.
2. Why should GlobalCommitter be removed in the new version of
Hi,
Flink 1.15 has developed a new feature to support different sink pre- and
post-topologies[1]. New metrics e.g. NumRecordsSend has been developed to
measure records sent to the external system. Metrics like "Bytes Sent" and
"Records Sent" measure records sent to the next task. So, in your
HI WuKong,
Afaiu, technically, you are not using Hbase secondary index(coprocessor).
What you are trying to do is to store the synced dim table in elasticsearch
and query from there to get the rowkeys and then use the rowkeys to get dim
table rows from Hbase. In this way, a (full) table scan in
Hi,
Thanks Martijn for driving this discussion. Your concerns are very
rational.
We should do our best to keep the Flink development on the right track. I
would suggest discussing it in a vision/goal oriented way. Since Flink has
a clear vision of unified batch and stream processing, supporting
Hi John,
your getKey() implementation shows that it is not deterministic, since
calling it with the same click instance multiple times will return
different keys. For example a call at 12:01:59.950 and a call at
12:02:00.050 with the same click instance will return two different keys:
Thanks @Martijn for driving this! +1 for deprecating and removing it. All
the concerns mentioned previously are valid. It is good to know that the
upcoming connector template/archetype will help the user for the kickoff.
Beyond that, speaking of using a real connector as a sample, since Flink is
Hi Meghajit,
like the exception described, parquet schema with nested columns is not
supported currently. It is on our todo list with high priority.
Best regards
Jing
On Fri, Jan 7, 2022 at 6:12 AM Meghajit Mazumdar <
meghajit.mazum...@gojek.com> wrote:
> Hello,
>
> Flink documentation
,
> false,
> true);
>
> Regards,
> Meghajit
>
> On Thu, Jan 6, 2022 at 3:43 PM Jing Ge wrote:
>
>> Hi Meghajit,
>>
>> thanks for asking. If you took a look at the source code
>
Hi Meghajit,
thanks for asking. If you took a look at the source code
https://github.com/apache/flink/blob/9bbadb9b105b233b7565af120020ebd8dce69a4f/flink-formats/flink-parquet/src/main/java/org/apache/flink/formats/parquet/ParquetVectorizedInputFormat.java#L174,
you should see Parquet MessageType
Hi,
thanks Martijn for bringing it up for discussion. I think we could make the
discussion a little bit clearer by splitting it into two questions:
1. should Flink drop Gelly?
2. should Flink drop the graph computing?
The answer of the first question could be yes, since there have been no
陈卓宇 你好，
在默认情况下，所有提交后的DML都是异步执行的，详见TableEnvironment.executeSql(String
statement)的注释。使用.await()和不使用.await()的区别是使用await()后会等待异步查询返回第一行结果（题外话：请注意INSERT和SELECT的区别），详见TableResult.await()注解，具体代码见TableResultImpl.awaitInternal(long
timeout, TimeUnit unit), 由于此时入参timeout为-1，导致future.get()被调用,
96 matches
Mail list logo
