Puneet Duggal created FLINK-32701:
-
Summary: Potential Memory Leak in Flink CEP due to Persistent
Starting States in NFAState
Key: FLINK-32701
URL: https://issues.apache.org/jira/browse/FLINK-32701
Pr
Thanks all for participating. I'm closing this vote in another thread.
Best,
Xintong
On Thu, Jul 27, 2023 at 11:37 AM Jiabao Sun
wrote:
> + 1 (non-binding)
>
> Thanks Xintong for driving this.
>
> Best,
> Jiabao
>
>
> On 2023/07/20 09:22:46 Xintong Song wrote:
> > Hi all,
> >
> > I'd like to
Hi devs,
I'm glad to announce that the must-have work items for release 2.0 [1] have
been approved. The voting thread is [2] and the discussions can be found in
[3][4].
There are 11 approving votes, 7 of which are binding:
- Xintong Song (binding)
- Yuan Mei (binding)
- Yu Li (binding)
- Leonard
Weihua Hu created FLINK-32702:
-
Summary: streaming examples could not run
Key: FLINK-32702
URL: https://issues.apache.org/jira/browse/FLINK-32702
Project: Flink
Issue Type: Bug
Componen
Hi Timo,
Thanks for the FLIP.
I also tend to think that Option 3 is better.
I would be also interested in a question mentioned by Benchao Li.
And a similar question about nested queries like
`SELECT * FROM (SELECT $rowtime, * FROM t);`
Am I right that it will show `$rowtime` in output ?
On Thu,
Hong Liang Teoh created FLINK-32703:
---
Summary: [hotfix] flink-python POM has a typo for protobuf-java in
shading config
Key: FLINK-32703
URL: https://issues.apache.org/jira/browse/FLINK-32703
Projec
Jiang Xin created FLINK-32704:
-
Summary: Supports spilling to disk when feedback channel memory
buffer is full
Key: FLINK-32704
URL: https://issues.apache.org/jira/browse/FLINK-32704
Project: Flink
Please remove me from your mailing list as don't want to receive emails
Regards
Divya
Hi Divya,
You'll need to send an email to dev-unsubscr...@flink.apache.org in order
to be unsubscribed.
Best regards,
Martijn
On Thu, Jul 27, 2023 at 2:18 PM Divya Sanghi
wrote:
> Please remove me from your mailing list as don't want to receive emails
>
>
> Regards
> Divya
>
Rui Fan created FLINK-32705:
---
Summary: Remove the beta for watermark alignment
Key: FLINK-32705
URL: https://issues.apache.org/jira/browse/FLINK-32705
Project: Flink
Issue Type: Sub-task
Hi Everyone,
Please review and vote on the release candidate #1 for the version 1.6.0 of
Apache Flink Kubernetes Operator,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Release Overview**
As an overview, the release consists of th
Hi Konstantin,
What you said makes sense. Dropping modules is an efficient option to
accelerate Flink evolution with acceptable function regressions. We should
do it constantly and strategically. On the other hand, we should point out
the core modules that must be backward compatible when a new ma
Hi Dong,
Thanks for your proposal. It is a very interesting feature and also a
complex one. Especially the "shotgun surgery"[1] of handling the
useProcessingTime logic. While reading the FLIP, I was wondering if it
possible to leverage the Visitor design pattern(not exactly use the pattern
directl
Hanyu Zheng created FLINK-32706:
---
Summary: Add SPLIT(STRING) support in SQL & Table API
Key: FLINK-32706
URL: https://issues.apache.org/jira/browse/FLINK-32706
Project: Flink
Issue Type: Improv
Thank you, Timo, for starting this FLIP!
I propose the following change:
Remove the requirement that DESCRIBE need to show system columns.
Some concrete vendor specific catalog implementations might prefer this
approach.
Usually the same system columns are available on all (or family) of tables
Hi Flinkers,
Wanted to check if anyone else has faced this issue before:
When Python UDF (which is used inside FlinkSQL) raises an exception, then
metrics get lost and not reported. Facing this issue both in Flink 1.16.2
and FLink 1.17.1 (Python 3.9).
If an exception is not raised, then metrics
>
> `SELECT * FROM (SELECT $rowtime, * FROM t);`
> Am I right that it will show `$rowtime` in output ?
Yes, all explicitly selected columns become a part of the result (and
intermediate) schema, and hence propagate.
On Thu, Jul 27, 2023 at 2:40 PM Alexey Leonov-Vendrovskiy <
vendrov...@gmail.com
liangjj created FLINK-32707:
---
Summary: the timestamp field precision should be set to 0 instead
of 1
Key: FLINK-32707
URL: https://issues.apache.org/jira/browse/FLINK-32707
Project: Flink
Issue Ty
Wencong Liu created FLINK-32708:
---
Summary: Fix the write logic in remote tier of hybrid shuffle
Key: FLINK-32708
URL: https://issues.apache.org/jira/browse/FLINK-32708
Project: Flink
Issue Type
Yuxin Tan created FLINK-32709:
-
Summary: Modify segment size to improve memory utilization for
Hybrid Shuffle
Key: FLINK-32709
URL: https://issues.apache.org/jira/browse/FLINK-32709
Project: Flink
Matthias, Markos, Martijn, thank you for your feedback.
Markos, I've addressed you feedback re: separating use cases from the Flink
capabilities. I think it is a positive change that will help new users
distinguish between the two.
Also attached screenshots for 'light mode'. I am personally part
21 matches
Mail list logo
