Sunyeop Lee created FLINK-33201:
---
Summary: Memory leak in CachingTopicSelector
Key: FLINK-33201
URL: https://issues.apache.org/jira/browse/FLINK-33201
Project: Flink
Issue Type: Bug
Hi devs,
Thanks everyone for your review and the votes!
I am happy to announce that FLIP-314: Support Customized Job Lineage
Listener [1] has been accepted.
There are 5 binding votes and 4 non-binding vote [2]:
- Jing Ge(binding)
- Feng Jin
- Leonard Xu(binding)
- Yangze Guo(binding)
- Yun
Thanks Rui, I check the codes and you're right.
As you described above, the entire process is actually two independent
steps from slot to TM and task to slot. Currenlty we use option
`cluster.evenly-spread-out-slots` for both of them. Can we provide
different options for the two steps, such as
Zhenqiu Huang created FLINK-33200:
-
Summary: ItemAt Expression validation fail in Table API due to
type mismatch
Key: FLINK-33200
URL: https://issues.apache.org/jira/browse/FLINK-33200
Project: Flink
Hi team,
I am looking to understand parity in Table API and SQL API.
Would you say that we have parity for UDF?
I see the TableAggregateFunction can not be represented in Flink SQL but
only in Table API. Have you known it to work like other UDFs?
Hi all, Thank you to everyone for the feedback on FLIP-239[1]. Based on the
discussion thread [2] and some offline discussions, we have come to a
consensus on the design and are ready to take a vote to contribute this to
Flink. I'd like to start a vote for it. The vote will be open for at least
72
Alexander Fedulov created FLINK-33199:
-
Summary: ArchitectureTests should test for canonical class names
instead of Class objects
Key: FLINK-33199
URL: https://issues.apache.org/jira/browse/FLINK-33199
Zhenqiu Huang created FLINK-33198:
-
Summary: Add timestamp with local time zone support in Avro
converters
Key: FLINK-33198
URL: https://issues.apache.org/jira/browse/FLINK-33198
Project: Flink
Hi everyone,
I've just opened a PR for the release announcement [1] and I am looking
forward to reviews and feedback.
Cheers,
Konstantin
[1] https://github.com/apache/flink-web/pull/680
Am Fr., 6. Okt. 2023 um 11:03 Uhr schrieb Sergey Nuyanzin <
snuyan...@gmail.com>:
> sorry for not
Thanks Yuepeng and Rui for driving this Discussion.
Internally when we try to use Flink 1.17.1 in production, we are also
suffering from the unbalanced task distribution problem for jobs with high
qps and complex dag. So +1 for the overall proposal.
Some questions about the details:
1, About
Liu Chong created FLINK-33197:
-
Summary: PyFlink support for ByteArraySchema
Key: FLINK-33197
URL: https://issues.apache.org/jira/browse/FLINK-33197
Project: Flink
Issue Type: New Feature
sorry for not mentioning it in previous mail
based on the reason above I'm
-1 (non-binding)
also there is one more issue [1]
which blocks all the externalised connectors testing against the most
recent commits in
to corresponding branches
[1] https://issues.apache.org/jira/browse/FLINK-33175
Hi Martjin,
Thanks for your comments. I also think it is better to decouple the connectors
– I agree they need to have their own release cycles. . I was worried that
moving to Flink 1.118 is somehow causing the Kafka connector to fail – i.e. a
regression. I think you are saying that there is no
13 matches
Mail list logo
