Thanks for letting us know, Xintong!
+1 from my side to merge the PR as this is just a minor change, plus this
could be a breaking change in the future if we don't accept it in this
release cycle.
Best,
Qingsheng
On Thu, Feb 2, 2023 at 12:08 PM Xintong Song wrote:
> Hi release managers,
>
>
>
Junrui Li created FLINK-30875:
-
Summary: Remove legacy AdaptiveBatchScheduler min parallelism
configuration call.
Key: FLINK-30875
URL: https://issues.apache.org/jira/browse/FLINK-30875
Project: Flink
Hi David,
Sorry I'm late to join discuss.
+1 for having a more structure doc about scheduler ecosystem and I can help
to fill in the details about batch part.
Best regards,
Weijie
David Morávek 于2023年2月1日周三 22:38写道：
> It makes sense to give the whole "scheduler ecosystem," not just the
> ad
Hi release managers,
I'd like to ask for your permissions to merge this PR [1]. It's a minor
improvement that changes the default behavior when both hybrid shuffle and
speculative execution are enabled, plus a few non-behavior-changing code
clean-ups. The PR has already passed CI and its impact s
Shammon created FLINK-30874:
---
Summary: Introduce configuration for table store
Key: FLINK-30874
URL: https://issues.apache.org/jira/browse/FLINK-30874
Project: Flink
Issue Type: Sub-task
Thank Martin for managing the release and all the people involved.
Best regards,
Weijie
Konstantin Knauf 于2023年2月2日周四 06:40写道：
> Great. Thanks, Martijn for managing the release.
>
> Am Mi., 1. Feb. 2023 um 20:26 Uhr schrieb Martijn Visser <
> martijnvis...@apache.org>:
>
> > The Apache Flink
Great. Thanks, Martijn for managing the release.
Am Mi., 1. Feb. 2023 um 20:26 Uhr schrieb Martijn Visser <
martijnvis...@apache.org>:
> The Apache Flink community is very happy to announce the release of Apache
> Flink 1.16.1, which is the first bugfix release for the Apache Flink 1.16
> series.
Yaroslav Tkachenko created FLINK-30873:
--
Summary: FileSystem Table API connector doesn't discover new files
when partitions are specified
Key: FLINK-30873
URL: https://issues.apache.org/jira/browse/FLINK-3087
The Apache Flink community is very happy to announce the release of Apache
Flink 1.16.1, which is the first bugfix release for the Apache Flink 1.16
series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
a
Martijn Visser created FLINK-30872:
--
Summary: Move GCP example to GCP connector repo
Key: FLINK-30872
URL: https://issues.apache.org/jira/browse/FLINK-30872
Project: Flink
Issue Type: Techni
Jun Zhang created FLINK-30871:
-
Summary: add bloom filter for orc
Key: FLINK-30871
URL: https://issues.apache.org/jira/browse/FLINK-30871
Project: Flink
Issue Type: Improvement
Compone
Hi Mason,
Thanks, [4] is indeed a copy-paste error and you've made the right
assumption that
https://repository.apache.org/content/repositories/orgapacheflink-1582/org/apache/flink/
is the correct maven central link.
I think we should use FLINK-30052 to move the Kafka connector code from the
1.17
It makes sense to give the whole "scheduler ecosystem," not just the
adaptive scheduler, a little bit more structure in the docs. We already
have 4 different schedulers (Default, Adaptive, AdaptiveBatch,
AdaptiveBatchSpeculative), and it becomes quite confusing since the details
are scattered aroun
Martijn Visser created FLINK-30870:
--
Summary: Performance regressions notifications in Slack are cut off
Key: FLINK-30870
URL: https://issues.apache.org/jira/browse/FLINK-30870
Project: Flink
Matthias Pohl created FLINK-30869:
-
Summary: Remove remote branches not being used anymore
Key: FLINK-30869
URL: https://issues.apache.org/jira/browse/FLINK-30869
Project: Flink
Issue Type: T
Hi all,
Fan, Jiang, Zhipeng, and I have created FLIP-289: Support online inference
(Flink ML).
The goal of this FLIP is to enable users to use the model trained by Flink
ML to do online inference. More details can be found in the FLIP doc at
https://cwiki.apache.org/confluence/pages/viewpage.acti
Thanks for clarification. I'm gonna leave the branch and document it
accordingly in [1].
[1]
https://cwiki.apache.org/confluence/display/FLINK/Flink+Release+Management
On Wed, Feb 1, 2023 at 1:29 PM Yun Tang wrote:
> I don't think we could use only flink-table-planner-blink related code to
> re
I don't think we could use only flink-table-planner-blink related code to
represent the whole blink branch. There still existed some code changes in
flink-runtime, flink-streaming-java, flink-yarn and some other modules.
However, some features are not included in the current flink main branch du
Hi all,
I make a mistake about the default value of the scope format
JobManagerOperatorScopeFormat. It should be
.jobmanager...
I have fixed it in the FLIP.
And the variables (task id and task name) have been added to the list.
Best,
Hang
Hang Ruan 于2023年2月1日周三 14:11写道：
> Hi all,
>
> > IIUC,
Shengkai Fang created FLINK-30868:
-
Summary: Revert to use LongSerializer for seralization in the
TimeIndicatorTypeInfo
Key: FLINK-30868
URL: https://issues.apache.org/jira/browse/FLINK-30868
Project:
yuzelin created FLINK-30867:
---
Summary: Support streaming read changes from overwrite
Key: FLINK-30867
URL: https://issues.apache.org/jira/browse/FLINK-30867
Project: Flink
Issue Type: New Feature
Jingsong Lee created FLINK-30866:
Summary: Introduce FileIO for table store
Key: FLINK-30866
URL: https://issues.apache.org/jira/browse/FLINK-30866
Project: Flink
Issue Type: Sub-task
The blink branch was created when Alibaba contributes its internal Flink
version to Flink Community, blink related code(e.g. flink-table-planner-blink,
flink-table-runtime-blink) have been adopted as the default code
(flink-table-planner, flink-table-runtime)[1], I think we can remove it now
s
+1 for Option 2, if we can abstract an "ReadableExecutionConfig"
interface(contains all is/get mehtod), and let ExecutionConfig implements
ReadableExecutionConfig
Best,
Lijie
João Boto 于2023年1月17日周二 20:39写道：
> Hi all,
>
> As establish a read-only contract seems to be consensual approach, talkin
Makes sense, let's move this discussion to JIRA instead of using this
closed vote thread!
Gyula
On Wed, Feb 1, 2023 at 12:08 PM Maximilian Michels wrote:
> +1 Not updating the generation id when the effective deployment spec
> does not change is an oversight, which we missed here, but it can be
Dong Lin created FLINK-30865:
Summary: Make pyflink-ml modules consistent with Flink ML Java
library packages
Key: FLINK-30865
URL: https://issues.apache.org/jira/browse/FLINK-30865
Project: Flink
Juntao Hu created FLINK-30864:
-
Summary: Optional pattern at the start of a group pattern not
working
Key: FLINK-30864
URL: https://issues.apache.org/jira/browse/FLINK-30864
Project: Flink
Issue
I'm documenting the branches that shouldn't be deleted in the release
management docs [1]. While going through the remote branches I noticed the
remote branch blink [2] which was created by Kurt in 2019. It feels like
that one could be deleted as well.
Are there any objections in deleting the blin
+1 Not updating the generation id when the effective deployment spec
does not change is an oversight, which we missed here, but it can be
fixed.
On Wed, Feb 1, 2023 at 2:07 AM Thomas Weise wrote:
>
> Hi,
>
> Sorry for the late reply to this thread, but in the meantime we learned that
> the assum
Yanfei Lei created FLINK-30863:
--
Summary: Do not delete the local changelog file of aborted
checkpoint
Key: FLINK-30863
URL: https://issues.apache.org/jira/browse/FLINK-30863
Project: Flink
Iss
Jing Ge created FLINK-30862:
---
Summary: Config doc generation should keep @deprecated ConfigOption
Key: FLINK-30862
URL: https://issues.apache.org/jira/browse/FLINK-30862
Project: Flink
Issue Type:
Chesnay, David:
Thank you guys for the extra information. We were clearly missing some
context here around the scheduler related efforts and the currently
available feature set.
As for the concrete suggestions regarding the docs.
1. If the adaptive scheduler provides a significantly different fe
+1 (non-binding)
* Verified hashes and signatures
* Verified no binaries
* Verified LICENSE and NOTICE files
* Verified poms point to 3.0.0-1.16
* Reviewed web PR
* Built from source
* Verified git tag
I think [4] your is a copy-paste error and I did all the verification
assuming that
https://rep
33 matches
Mail list logo
