Hi Shammon, Hi Xiangyu,
Thanks for bringing this to our attention. I can see this is a great
proposal born from real business scenarios. +1 for it.
People have been keen to use one platform to cover all their data
production and consumption requirements. Flink did a great job for the
production,
lincoln lee created FLINK-32824:
---
Summary: Port Calcite's fix for the sql like operator
Key: FLINK-32824
URL: https://issues.apache.org/jira/browse/FLINK-32824
Project: Flink
Issue Type: Bug
Thanks for bringing up this discussion, Shammon. I would like to share some of
my observations and experiences.
Flink has almost become the de facto standard for streaming computing, and
Flink batch have been successfully applied in some companies. If Flink can
support OLAP scenarios well, a
Hi, Allison
Thanks for driving this proposal, it looks cool for batch jobs under
application mode. But after reading your FLIP document and [1], I have a
question. Why do you want to rename the execution.attached configuration to
client.attached.after.submission and at the same time deprecate
Rui Fan created FLINK-32823:
---
Summary: Update the adaptive scheduler doc about batch job
limitation
Key: FLINK-32823
URL: https://issues.apache.org/jira/browse/FLINK-32823
Project: Flink
Issue
Zhanghao Chen created FLINK-32822:
-
Summary: Add connector option to control whether to enable
auto-commit of offsets when checkpoints is enabled
Key: FLINK-32822
URL:
Zhanghao Chen created FLINK-32821:
-
Summary: Streaming examples failed to execute due to error in
packaging
Key: FLINK-32821
URL: https://issues.apache.org/jira/browse/FLINK-32821
Project: Flink
Zhanghao Chen created FLINK-32820:
-
Summary: ParameterTool is mistakenly marked as deprecated
Key: FLINK-32820
URL: https://issues.apache.org/jira/browse/FLINK-32820
Project: Flink
Issue
Jun Zhang created FLINK-32819:
-
Summary: flink can not parse the param `#` correctly in k8s
application mode
Key: FLINK-32819
URL: https://issues.apache.org/jira/browse/FLINK-32819
Project: Flink
Thanks Danny and Jiabao for driving the work!
+1 (binding)
- built from source code succeeded
- verified signatures
- verified hashsums
- checked release notes
- reviewed the web PR
Best,
Leonard
> On Aug 6, 2023, at 6:58 PM, Ahmed Hamdy wrote:
>
> Thanks Danny
> + 1 (non-binding)
>
>
Xianxun Ye created FLINK-32817:
--
Summary: Supports running jar file names with Spaces
Key: FLINK-32817
URL: https://issues.apache.org/jira/browse/FLINK-32817
Project: Flink
Issue Type:
Rui Fan created FLINK-32818:
---
Summary: Support region failover for adaptive scheduler
Key: FLINK-32818
URL: https://issues.apache.org/jira/browse/FLINK-32818
Project: Flink
Issue Type: Improvement
+1 (binding)
-Max
On Tue, Aug 8, 2023 at 10:56 AM Etienne Chauchot wrote:
>
> Hi all,
>
> As part of Flink bylaws, binding votes for FLIP changes are active
> committer votes.
>
> Up to now, we have only 2 binding votes. Can one of the committers/PMC
> members vote on this FLIP ?
>
> Thanks
>
>
Congrats, YanFei!
Jing Ge 于2023年8月8日周二 17:41写道:
> Congrats, YanFei!
>
> Best regards,
> Jing
>
> On Tue, Aug 8, 2023 at 3:04 PM Yangze Guo wrote:
>
> > Congrats, Yanfei!
> >
> > Best,
> > Yangze Guo
> >
> > On Tue, Aug 8, 2023 at 9:20 AM yuxia
> wrote:
> > >
> > > Congratulations, Yanfei!
> >
Congrats, Hangxiang!
Jing Ge 于2023年8月8日周二 17:44写道:
> Congrats, Hangxiang!
>
> Best regards,
> Jing
>
> On Tue, Aug 8, 2023 at 3:04 PM Yangze Guo wrote:
>
> > Congrats, Hangxiang!
> >
> > Best,
> > Yangze Guo
> >
> > On Tue, Aug 8, 2023 at 11:28 AM yh z wrote:
> > >
> > > Congratulations,
Congratulations, Matthias!
Maximilian Michels 于2023年8月8日周二 17:54写道:
> Congrats, well done, and welcome to the PMC Matthias!
>
> -Max
>
> On Tue, Aug 8, 2023 at 8:36 AM yh z wrote:
> >
> > Congratulations, Matthias!
> >
> > Best,
> > Yunhong Zheng (Swuferhong)
> >
> > Ryan Skraba 于2023年8月7日周一
Rui Fan created FLINK-32816:
---
Summary: Remove the local recovery limitation for adaptive
scheduler limitation
Key: FLINK-32816
URL: https://issues.apache.org/jira/browse/FLINK-32816
Project: Flink
Thank you Shammon for initiating this discussion. As one of the Flink OLAP
developers in ByteDance, I would also like to share a real case of our
users.
About two years ago we found our first OLAP user internally by integrating
Flink OLAP with ByteHTAP. Users are willing to use Flink as an OLAP
18 matches
Mail list logo