Hi Matthias,
Thanks for letting us know! After discussed with 1.19 release managers, we
agreed to merge these pr.
Thank you for the work on GHA workflows!
Best,
Yun, Jing, Martijn and Lincoln
Matthias Pohl 于2024年1月30日周二 22:20写道：
> Thanks for the update, Lincoln.
>
> fyi: I merged FLINK-32684
Thanks for driving this Leonard!
+1 (binding)
- Release notes look ok
- Signatures/checksums of source archive are good
- Verified there are no binaries in the source archive
- Built sources locally successfully
- v1.0.0-rc2 tag exists in github
- Tag build passing on CI [1]
- Contents of Maven d
Qingsheng Ren created FLINK-34317:
-
Summary: Cleanup pending Flink CDC issues on GitHub
Key: FLINK-34317
URL: https://issues.apache.org/jira/browse/FLINK-34317
Project: Flink
Issue Type: Sub-
Gyula Fora created FLINK-34318:
--
Summary: AdaptiveScheduler resource stabilisation should happen
before the job is cancelled
Key: FLINK-34318
URL: https://issues.apache.org/jira/browse/FLINK-34318
Projec
ConradJam created FLINK-34319:
-
Summary: Bump okhttp version to 4.12.0
Key: FLINK-34319
URL: https://issues.apache.org/jira/browse/FLINK-34319
Project: Flink
Issue Type: Improvement
Com
Hi,
[x] -1, Do not approve the release (please provide specific comments)
I wanted clarifications on our thinking around the following.
In the source code
https://github.com/apache/flink-connector-jdbc/releases/tag/v3.1.2-rc2
* This release introduces (I assume experimental, like Flink’s st
Hi David, thanks for your feedback
> This release introduces (I assume experimental, like Flink’s statement
around Java compatibility but we have not documented this as experimental)
support for Java 17. I see
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/java_compatibility/
Sorry for the late reply.
> So you would have a high data skew while 1 subtask is receiving all the
data, but on average (say over 1-2 days) data skew would come down to 0
because all subtasks would have received their portion of the data.
> I'm inclined to think that the current proposal might s
Martijn Visser created FLINK-34320:
--
Summary: Flink Kafka connector tests time out
Key: FLINK-34320
URL: https://issues.apache.org/jira/browse/FLINK-34320
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-34321:
-
Summary: Make nightly trigger select the release branch
automatically
Key: FLINK-34321
URL: https://issues.apache.org/jira/browse/FLINK-34321
Project: Flink
Matthias Pohl created FLINK-34322:
-
Summary: Make secrets work in GitHub Action workflows
Key: FLINK-34322
URL: https://issues.apache.org/jira/browse/FLINK-34322
Project: Flink
Issue Type: Su
xuyang created FLINK-34323:
--
Summary: Session window tvf failed when using named params
Key: FLINK-34323
URL: https://issues.apache.org/jira/browse/FLINK-34323
Project: Flink
Issue Type: Bug
Hi everyone,
I merged the changes related to FLIP-396 [1] into master and release-1.18.
This enables the Flink CI and nightly builds [2] for these two versions
(and any branches that are based on these changes). The GitHub Actions
(GHA) workflows are still in beta stage, i.e. we should still base o
Matthias Pohl created FLINK-34324:
-
Summary: s3_setup is called in test_file_sink.sh even if the
common_s3.sh is not sourced
Key: FLINK-34324
URL: https://issues.apache.org/jira/browse/FLINK-34324
Pro
Alexis Sarda-Espinosa created FLINK-34325:
-
Summary: Inconsistent state with data loss after OutOfMemoryError
in Job Manager
Key: FLINK-34325
URL: https://issues.apache.org/jira/browse/FLINK-34325
Matthias Pohl created FLINK-34326:
-
Summary: Add Slack integration
Key: FLINK-34326
URL: https://issues.apache.org/jira/browse/FLINK-34326
Project: Flink
Issue Type: Sub-task
Repo
Hi Rui,
" and provide the total and current score in the detailed tab. I didn't see the
detailed design in the FLIP, would you mind
improve the design doc? Thanks".
It will essentially be a basic list view similar to the "Checkpoints" tab. I
only briefly mentioned this in the FLIP because it wi
Mason Chen created FLINK-34327:
--
Summary: Use maven wrapper in operator build
Key: FLINK-34327
URL: https://issues.apache.org/jira/browse/FLINK-34327
Project: Flink
Issue Type: Improvement
Thanks Sergey for driving this!
-1(binding) as we discussed on the web PR[1], looking forward next RC.
Best,
Leonard
[1] https://github.com/apache/flink-web/pull/707#discussion_r1471090061
> 2024年1月30日 上午8:17，Sergey Nuyanzin 写道：
>
> Hi everyone,
> Please review and vote on the release candida
Hi Martijn, Ferenc
Thanks all for driving this. As Ferenc said, HBase 1.x is dead, so on the
way forward it should be safe to drop it. Same view as mine. So +1 for this.
Best!
tanjialiang
Replied Message
>From Ferenc Csaky
Date 1/30/2024 22:14
To
Subject Re: [DISCUSS] Drop support f
Hi Weijie and Xingtong,
Thanks for the reply! Please see my comments below.
> Does this mean if we want to support (KeyedStream, BroadcastStream) ->
> (KeyedStream), we must make sure that no data can be output upon processing
> records from the input BroadcastStream? That's probably a reasonable
> I was thinking about using the existing numRecordsInPerSecond metric
numRecordsInPerSecond sounds make sense to me, and I think
it's necessary to mention it in the FLIP wiki. It will let other developers
to easily understand. WDYT?
BTW, that's why I ask whether the data skew score means total
r
OK, I see your point.
I think the demand for updating states and emitting outputs upon receiving
a broadcast record makes sense. However, the way
`KeyedBroadcastProcessFunction` supports this may not be optimal. E.g., if
`Collector#collect` is called in `processBroadcastElement` but outside of
`Co
Zhanghao Chen created FLINK-34328:
-
Summary: Release Testing Instructions: Verify FLINK-34037 Improve
Serialization Configuration And Usage In Flink
Key: FLINK-34328
URL: https://issues.apache.org/jira/browse/FLIN
Hi Devs,
I recently worked with the Open Lineage community on this topic. I feel the
open lineage community gives a very good idea to define an intermediate
representation (Dataset) about the metadata of a since/sink. Also
LineageVertex could definitely have multiple datasets, for example Hybrid
s
Gyula Fora created FLINK-34329:
--
Summary: ScalingReport format tests fail locally on decimal format
Key: FLINK-34329
URL: https://issues.apache.org/jira/browse/FLINK-34329
Project: Flink
Issue T
Thanks everyone for the feedback
This RC is cancelled and a new one will be created
On Thu, Feb 1, 2024 at 2:42 AM Leonard Xu wrote:
> Thanks Sergey for driving this!
>
> -1(binding) as we discussed on the web PR[1], looking forward next RC.
>
> Best,
> Leonard
> [1] https://github.com/apache/f
27 matches
Mail list logo
