Hi everyone,
I'm pleased to announce that we have unanimously approved this release
candidate:
There are 13 approving votes, 4 of which are binding:
- Lijie Wang (non-binding)
- Jing Ge (non-binding)
- Yuxia Luo (non-binding)
- Martijn Visser (binding)
- Dong Lin (binding)
- Ran Tao
Hi yuxia
Thanks for initiating this discussion.
There are usually two types of data deletion in a production environment:
one is deleting data directly and the other is moving the data to the trash
directory which will be deleted periodically by the underlying system.
Can we distinguish between
Hi everyone,
Thanks for the valuable comments!
Excited to see this is an area of interest for the community!
Summarizing some of the main points raised along with my thoughts:
- Labels (Key/Value) pairs are more expressive than Tags (Strings) so
using the former is a good idea — I am
Jark Wu created FLINK-31576:
---
Summary: Add JavaDoc that SqlNodeConverter.getCatalogManager is
discouraged to use
Key: FLINK-31576
URL: https://issues.apache.org/jira/browse/FLINK-31576
Project: Flink
Hi all,
Thank you Panagiotis for proposing this. From the size of the thread, this is a
much needed feature in Flink!
Some thoughts, to extend those already adeptly summarised by Piotr, Matthias
and Jing.
- scope of FLIP: +1 to scoping this FLIP to observability around a restart.
That would
Hi, devs.
I'd like to start a discussion about FLIP-302: Support TRUNCATE TABLE statement
[1].
The TRUNCATE TABLE statement is a SQL command that allows users to quickly and
efficiently delete all rows from a table without dropping the table itself.
This statement is commonly used in data
Hello dear Flink team
We are rather new to Flink and having problems understanding how unit
testing works overall.
We want to test the* onTimer()* method after registering a timer in the
*processElement()* function. However, the *onTimer() *is never called.
We were investigating the
luoyuxia created FLINK-31575:
Summary: Don't swap table-planner-loader and table-planner to use
hive dialect
Key: FLINK-31575
URL: https://issues.apache.org/jira/browse/FLINK-31575
Project: Flink
Hi Yu,
Thanks for the input! I created FLINK-31573 [1] for tracking this issue. I
didn't mark this as a blocker of releasing 1.17.0 as your latest test
suggests that the performance of 1.17.0 doesn't drop compared with 1.16. As
discussed it looks like something that has already existed for
Ran Tao created FLINK-31574:
---
Summary: Cleanup unused private methods in OperationConverterUtils
Key: FLINK-31574
URL: https://issues.apache.org/jira/browse/FLINK-31574
Project: Flink
Issue Type:
Qingsheng Ren created FLINK-31573:
-
Summary: Nexmark performance drops in 1.17 compared with 1.13
Key: FLINK-31573
URL: https://issues.apache.org/jira/browse/FLINK-31573
Project: Flink
Issue
Hi Leonard and Yun,
Thanks to Yun Gao for the reminder.
We quickly re-run the test q18 in Nexmark for Flink 1.16.1 and Flink 1.17
with configuration
`execution.checkpointing.checkpoints-after-tasks-finish.enabled: false`.
The last few metrics of cpu usage behaved normally, which proves that the
Matthias Pohl created FLINK-31572:
-
Summary: Other announcements
Key: FLINK-31572
URL: https://issues.apache.org/jira/browse/FLINK-31572
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-31571:
-
Summary: Apache mailing lists announcements
Key: FLINK-31571
URL: https://issues.apache.org/jira/browse/FLINK-31571
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-31570:
-
Summary: Remove outdated versions
Key: FLINK-31570
URL: https://issues.apache.org/jira/browse/FLINK-31570
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-31568:
-
Summary: Update japicmp configuration
Key: FLINK-31568
URL: https://issues.apache.org/jira/browse/FLINK-31568
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-31569:
-
Summary: Merge website pull request
Key: FLINK-31569
URL: https://issues.apache.org/jira/browse/FLINK-31569
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-31567:
-
Summary: Promote the release
Key: FLINK-31567
URL: https://issues.apache.org/jira/browse/FLINK-31567
Project: Flink
Issue Type: New Feature
Matthias Pohl created FLINK-31566:
-
Summary: Publish the Dockerfiles for the new release
Key: FLINK-31566
URL: https://issues.apache.org/jira/browse/FLINK-31566
Project: Flink
Issue Type:
Matthias Pohl created FLINK-31565:
-
Summary: Create Git tag and mark version as released in Jira
Key: FLINK-31565
URL: https://issues.apache.org/jira/browse/FLINK-31565
Project: Flink
Issue
Matthias Pohl created FLINK-31564:
-
Summary: Deploy artifacts to Maven Central Repository
Key: FLINK-31564
URL: https://issues.apache.org/jira/browse/FLINK-31564
Project: Flink
Issue Type:
Matthias Pohl created FLINK-31563:
-
Summary: Deploy Python artifacts to PyPI
Key: FLINK-31563
URL: https://issues.apache.org/jira/browse/FLINK-31563
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-31562:
-
Summary: Finalize release 1.17.0
Key: FLINK-31562
URL: https://issues.apache.org/jira/browse/FLINK-31562
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-31561:
-
Summary: flink-master-regression-check is failing since March 15,
2023
Key: FLINK-31561
URL: https://issues.apache.org/jira/browse/FLINK-31561
Project: Flink
Hi Yu,
The waiting mentioned here should be introduced in [1][2] in 1.15
to fix the semantic issue of two-phase commit sinks.
If it is not a concern to ensure all the data get committed
for the bounded-inputs jobs, you may re-run the performance tests
with final checkpoint disabled:
Hi, Yu Chen
> The test results show that Flink 1.17 has a significant performance
> degradation compared to Flink 1.13 (About 8.49%), shall we need to identify
> the reason for the performance degradation before Flink 1.17 is released?
Thanks for the verification, I wonder why you compared to
Hi Chesnay,
Thanks for the release and for upgrading the Cassandra connector parent.
Best
Etienne
Le 22/03/2023 à 10:21, Chesnay Schepler a écrit :
The release of flink-connector-parent 1.0.0 is complete.
Update your connectors everyone. Let's get rid of the strange "zentol"
thing.
Hi Qingshen again,
I just did an in-depth review of the release notes as promised. I have
not opened the jira tickets though.
PTAL
Best
Etienne
Le 22/03/2023 à 08:43, Qingsheng Ren a écrit :
Hi Jakub,
Thanks for reviewing the release note and welcome to the Flink community!
We will
Fan Yang created FLINK-31560:
Summary: Issue deleting Flink cluster due to savepoint failing to
complete
Key: FLINK-31560
URL: https://issues.apache.org/jira/browse/FLINK-31560
Project: Flink
Hi, all.
We have built a Standalone Cluster based on Flink 1.17-RC3 release package
with 8 TMs with Nexmark[1].
The test results show that Flink 1.17 has a significant performance
degradation compared to Flink 1.13 (About 8.49%), shall we need to identify
the reason for the performance
The release of flink-connector-parent 1.0.0 is complete.
Update your connectors everyone. Let's get rid of the strange "zentol"
thing.
Hang Ruan created FLINK-31559:
-
Summary: Update the flink version to 1.18-SNAPSHOT in
flink-connector-kafka
Key: FLINK-31559
URL: https://issues.apache.org/jira/browse/FLINK-31559
Project: Flink
Hi Qingsheng,
Yes indeed I was referring to the jira release notes. I know they are
generated, I was wondering if we could configure the generation process.
Anyway, the human readable release notes are clear enough. I'll review
the related PR.
Best
Etienne
Le 22/03/2023 à 09:14, Qingsheng
Hi Etienne,
Thanks for the review!
I guess you are referring to the JIRA release note [1]. I didn't find a
place to configure the format of it, as it is auto-generated by JIRA.
Actually there will be a more "human-readable" release note [1] for users
in the document, which highlights breaking
Caizhi Weng created FLINK-31558:
---
Summary: Support updating schema type with restrictions in CDC
sink of Table Store
Key: FLINK-31558
URL: https://issues.apache.org/jira/browse/FLINK-31558
Project:
Hi Jakub,
Thanks for reviewing the release note and welcome to the Flink community!
We will change the fix version of all open issues to 1.17.1 in batch before
the final release, then these issues will disappear from the release note
auto-generated by JIRA.
Please feel free to raise any doubts
Hi all,
I’m reaching out today for some suggestions (and hopefully a solution) for a
Flink job that I’m working on. The job itself reads JSON strings from a Kafka
topic and reads those into JSONObjects (currently via Gson), which are then
operated against, before ultimately being written out
Hi all,
I’m reaching out today for some suggestions (and hopefully a solution) for a
Flink job that I’m working on. The job itself reads JSON strings from a Kafka
topic and reads those into JSONObjects (currently via Gson), which are then
operated against, before ultimately being written out
Hi,
I was looking through release notes [1], and found one the list some
tasks, that have status "Open". For example: FLINK-28538 [2], FLINK-19722
[2], FLINK-18873 [3]. Is this situation expected, or should these tasks be
removed from release notes?
This is my first message on this mailing list,
+1 (binding)
Note, in the NOTICE files, the copyright year is still only until 2022. I
don't think it's a blocker, but should be updated.
+ Checked the website update
+ checked the source archive for copied code (no licenses are listed in the
root NOTICE file)
+ src archive contents build
40 matches
Mail list logo
