Saketh Kurnool created FLINK-35830:
--
Summary: Large failed bulk request can result in TM OOM
Key: FLINK-35830
URL: https://issues.apache.org/jira/browse/FLINK-35830
Project: Flink
Issue Type
Hi Xintong,
Thanks for your comments.
However, my major concern after reading this FLIP is that, the current
> design might be too complicated. It tries take all possible kinds of events
> (timestamp watermark, end-of-data, end-of-partition, internal watermark,
> and arbitrary user defined waterm
+1 on this. Thank you, Zhanghao!
Cheers,
Matyas
On Fri, Jul 12, 2024 at 5:58 PM Becket Qin wrote:
> Thanks for the proposal, Zhanghao.
>
> +1 on the proposal. It makes a lot of sense.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
>
> On Tue, May 28, 2024 at 7:43 PM Zhanghao Chen
> wrote:
>
> > Hi al
Thanks for the proposal, Zhanghao.
+1 on the proposal. It makes a lot of sense.
Thanks,
Jiangjie (Becket) Qin
On Tue, May 28, 2024 at 7:43 PM Zhanghao Chen
wrote:
> Hi all,
>
> I'd like start a discussion on FLIP-460: Display source/sink I/O metrics
> on Flink Web UI [1].
>
> Currently, the
Hi all,
Thanks for your feedback. Below are my thoughts on the questions you've
raised
@Fabian
- What is the future plan for job submissions in Flink? With the current
> proposal, Flink will support JobGraph/StreamGraph/compiled plan
> submissions? It might be confusing for users and complicate
xuyang created FLINK-35829:
--
Summary: StreamPhysicalWindowTableFunction doesn't always require
watermark
Key: FLINK-35829
URL: https://issues.apache.org/jira/browse/FLINK-35829
Project: Flink
Issue
Qishang Zhong created FLINK-35828:
-
Summary: NullArgumentException when accessing the checkpoint API
concurrently
Key: FLINK-35828
URL: https://issues.apache.org/jira/browse/FLINK-35828
Project: Flink
yisha zhou created FLINK-35827:
--
Summary: Equality bewteen a row field and a row constant is wrong
in SQL
Key: FLINK-35827
URL: https://issues.apache.org/jira/browse/FLINK-35827
Project: Flink
Hi love_h1...@126.com,
Thanks for reaching out to the Flink community. Just a few general remarks:
- Flink's Jira [1] should be used to report potential bugs. The dev mailing
list is used for design and community-related discussions.
- It's also useful to provide not only snippets of the logs but a