[jira] [Assigned] (FLINK-35331) Download links for binary releases are displayed as source releases on website
[ https://issues.apache.org/jira/browse/FLINK-35331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-35331: --- Assignee: Hector Sanchez > Download links for binary releases are displayed as source releases on website > -- > > Key: FLINK-35331 > URL: https://issues.apache.org/jira/browse/FLINK-35331 > Project: Flink > Issue Type: Bug > Components: Project Website >Reporter: Xintong Song >Assignee: Hector Sanchez >Priority: Major > Labels: pull-request-available > > Take Pre-bundled Hadoop as examples. The content for downloading are binary > releases, while the link is displayed as "Pre-bundled Hadoop 2.x.y Source > Release (asc, sha512)". The problem is caused by misusing > `source_release_[url|asc_url|sha512_url]` for binary contents in the > corresponding [yaml > file.|https://github.com/apache/flink-web/blob/asf-site/docs/data/additional_components.yml] > There are many similar cases in the webpage. > And a relevant issues is that, some source releases are displayed as "XXX > Source Release Source Release", due to including "Source Release" in the > `name` field of the corresponding yaml file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-32622) Do not add mini-batch assigner operator if it is useless
[ https://issues.apache.org/jira/browse/FLINK-32622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842242#comment-17842242 ] Jing Ge commented on FLINK-32622: - 1.19: c370b20c8e2d1ea55dd1fc4c283430832d9f9aae > Do not add mini-batch assigner operator if it is useless > > > Key: FLINK-32622 > URL: https://issues.apache.org/jira/browse/FLINK-32622 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Affects Versions: 1.19.0 >Reporter: Fang Yong >Assignee: Jeyhun Karimov >Priority: Major > Labels: pull-request-available > Fix For: 1.20.0 > > > Currently if user config mini-batch for their sql jobs, flink will always add > mini-batch assigner operator in job plan even there's no agg/join operators > in the job. Mini-batch operator will generate useless event and cause > performance issue for them. If the mini-batch is useless for the specific > jobs, flink should not add mini-batch assigner even when users turn on > mini-batch mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-32622) Do not add mini-batch assigner operator if it is useless
[ https://issues.apache.org/jira/browse/FLINK-32622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841817#comment-17841817 ] Jing Ge commented on FLINK-32622: - [~jeyhunkarimov] could you please backport it to 1.19? > Do not add mini-batch assigner operator if it is useless > > > Key: FLINK-32622 > URL: https://issues.apache.org/jira/browse/FLINK-32622 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Affects Versions: 1.19.0 >Reporter: Fang Yong >Assignee: Jeyhun Karimov >Priority: Major > Labels: pull-request-available > Fix For: 1.20.0 > > > Currently if user config mini-batch for their sql jobs, flink will always add > mini-batch assigner operator in job plan even there's no agg/join operators > in the job. Mini-batch operator will generate useless event and cause > performance issue for them. If the mini-batch is useless for the specific > jobs, flink should not add mini-batch assigner even when users turn on > mini-batch mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FLINK-32622) Do not add mini-batch assigner operator if it is useless
[ https://issues.apache.org/jira/browse/FLINK-32622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge resolved FLINK-32622. - Fix Version/s: 1.20.0 Resolution: Fixed > Do not add mini-batch assigner operator if it is useless > > > Key: FLINK-32622 > URL: https://issues.apache.org/jira/browse/FLINK-32622 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Affects Versions: 1.19.0 >Reporter: Fang Yong >Assignee: Jeyhun Karimov >Priority: Major > Labels: pull-request-available > Fix For: 1.20.0 > > > Currently if user config mini-batch for their sql jobs, flink will always add > mini-batch assigner operator in job plan even there's no agg/join operators > in the job. Mini-batch operator will generate useless event and cause > performance issue for them. If the mini-batch is useless for the specific > jobs, flink should not add mini-batch assigner even when users turn on > mini-batch mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-32622) Do not add mini-batch assigner operator if it is useless
[ https://issues.apache.org/jira/browse/FLINK-32622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841816#comment-17841816 ] Jing Ge commented on FLINK-32622: - master: b1544e4e513d2b75b350c20dbb1c17a8232c22fd > Do not add mini-batch assigner operator if it is useless > > > Key: FLINK-32622 > URL: https://issues.apache.org/jira/browse/FLINK-32622 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Affects Versions: 1.19.0 >Reporter: Fang Yong >Assignee: Jeyhun Karimov >Priority: Major > Labels: pull-request-available > > Currently if user config mini-batch for their sql jobs, flink will always add > mini-batch assigner operator in job plan even there's no agg/join operators > in the job. Mini-batch operator will generate useless event and cause > performance issue for them. If the mini-batch is useless for the specific > jobs, flink should not add mini-batch assigner even when users turn on > mini-batch mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-32622) Do not add mini-batch assigner operator if it is useless
[ https://issues.apache.org/jira/browse/FLINK-32622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-32622: --- Assignee: Jeyhun Karimov > Do not add mini-batch assigner operator if it is useless > > > Key: FLINK-32622 > URL: https://issues.apache.org/jira/browse/FLINK-32622 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Affects Versions: 1.19.0 >Reporter: Fang Yong >Assignee: Jeyhun Karimov >Priority: Major > Labels: pull-request-available > > Currently if user config mini-batch for their sql jobs, flink will always add > mini-batch assigner operator in job plan even there's no agg/join operators > in the job. Mini-batch operator will generate useless event and cause > performance issue for them. If the mini-batch is useless for the specific > jobs, flink should not add mini-batch assigner even when users turn on > mini-batch mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FLINK-34562) Port Debezium Avro Confluent changes (FLINK-34509) to Chinese
[ https://issues.apache.org/jira/browse/FLINK-34562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge closed FLINK-34562. --- Fix Version/s: 1.20.0 Resolution: Fixed > Port Debezium Avro Confluent changes (FLINK-34509) to Chinese > - > > Key: FLINK-34562 > URL: https://issues.apache.org/jira/browse/FLINK-34562 > Project: Flink > Issue Type: Improvement > Components: chinese-translation, Documentation >Reporter: Lorenzo Affetti >Assignee: Vincent Woo >Priority: Minor > Labels: pull-request-available > Fix For: 1.20.0 > > > Port the changes applied in > [https://issues.apache.org/jira/projects/FLINK/issues/FLINK-34509] to the > Chinese version of the documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34562) Port Debezium Avro Confluent changes (FLINK-34509) to Chinese
[ https://issues.apache.org/jira/browse/FLINK-34562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832105#comment-17832105 ] Jing Ge commented on FLINK-34562: - master: 3841f0622552674fe0013b89605594a401cb6902 > Port Debezium Avro Confluent changes (FLINK-34509) to Chinese > - > > Key: FLINK-34562 > URL: https://issues.apache.org/jira/browse/FLINK-34562 > Project: Flink > Issue Type: Improvement > Components: chinese-translation, Documentation >Reporter: Lorenzo Affetti >Assignee: Vincent Woo >Priority: Minor > Labels: pull-request-available > > Port the changes applied in > [https://issues.apache.org/jira/projects/FLINK/issues/FLINK-34509] to the > Chinese version of the documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-34562) Port Debezium Avro Confluent changes (FLINK-34509) to Chinese
[ https://issues.apache.org/jira/browse/FLINK-34562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34562: --- Assignee: Vincent Woo > Port Debezium Avro Confluent changes (FLINK-34509) to Chinese > - > > Key: FLINK-34562 > URL: https://issues.apache.org/jira/browse/FLINK-34562 > Project: Flink > Issue Type: Improvement > Components: chinese-translation, Documentation >Reporter: Lorenzo Affetti >Assignee: Vincent Woo >Priority: Minor > Labels: pull-request-available > > Port the changes applied in > [https://issues.apache.org/jira/projects/FLINK/issues/FLINK-34509] to the > Chinese version of the documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FLINK-34640) Replace DummyMetricGroup usage with UnregisteredMetricsGroup
[
https://issues.apache.org/jira/browse/FLINK-34640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge closed FLINK-34640.
---
Resolution: Fixed
> Replace DummyMetricGroup usage with UnregisteredMetricsGroup
>
>
> Key: FLINK-34640
> URL: https://issues.apache.org/jira/browse/FLINK-34640
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Metrics, Tests
>Reporter: Chesnay Schepler
>Assignee: Jeyhun Karimov
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
>
> The {{DummyMetricGroup}} is terrible because it is decidedly unsafe to use.
> Use the {{UnregisteredMetricsGroup}} instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34640) Replace DummyMetricGroup usage with UnregisteredMetricsGroup
[
https://issues.apache.org/jira/browse/FLINK-34640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827076#comment-17827076
]
Jing Ge commented on FLINK-34640:
-
master: a0c811ec03d51c3b184c28f6f58b79466061ae71
> Replace DummyMetricGroup usage with UnregisteredMetricsGroup
>
>
> Key: FLINK-34640
> URL: https://issues.apache.org/jira/browse/FLINK-34640
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Metrics, Tests
>Reporter: Chesnay Schepler
>Assignee: Jeyhun Karimov
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
>
> The {{DummyMetricGroup}} is terrible because it is decidedly unsafe to use.
> Use the {{UnregisteredMetricsGroup}} instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34640) Replace DummyMetricGroup usage with UnregisteredMetricsGroup
[
https://issues.apache.org/jira/browse/FLINK-34640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34640:
---
Assignee: Jeyhun Karimov
> Replace DummyMetricGroup usage with UnregisteredMetricsGroup
>
>
> Key: FLINK-34640
> URL: https://issues.apache.org/jira/browse/FLINK-34640
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Metrics, Tests
>Reporter: Chesnay Schepler
>Assignee: Jeyhun Karimov
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
>
> The {{DummyMetricGroup}} is terrible because it is decidedly unsafe to use.
> Use the {{UnregisteredMetricsGroup}} instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-25325: Description: Based on the consensus from the mailing list discussion[1][2], we have been starting working on the JUnit4 to JUnit5 migration. This is the umbrella ticket which describes the big picture of the migration with following steps: * AssertJ integration and guideline * Test Framework upgrade from JUnit4 to JUnit5 * JUnit5 migration guideline(document and reference migration) * Optimization for issues found while writing new test in JUint5 * [Long-term]Module based graceful migration of old tests in JUnit4 to JUnit5 All JUnit5 migration related tasks are welcome to be created under this umbrella. [https://github.com/apache/flink/pull/24483] is an excellent PR as example. Please create similar Brief change log summary for new PR. [1] [[DISCUSS]Moving to JUnit5|https://lists.apache.org/thread/jsjvc2cqb91pyh47d4p6olk3c1vxqm3w] [2] [[DISCUSS] Conventions on assertions to use in tests|https://lists.apache.org/thread/33t7hz8w873p1bc5msppk65792z08rgt] [3] [JUnit5 migration guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] was: Based on the consensus from the mailing list discussion[1][2], we have been starting working on the JUnit4 to JUnit5 migration. This is the umbrella ticket which describes the big picture of the migration with following steps: * AssertJ integration and guideline * Test Framework upgrade from JUnit4 to JUnit5 * JUnit5 migration guideline(document and reference migration) * Optimization for issues found while writing new test in JUint5 * [Long-term]Module based graceful migration of old tests in JUnit4 to JUnit5 All JUnit5 migration related tasks are welcome to be created under this umbrella. [1] [[DISCUSS]Moving to JUnit5|https://lists.apache.org/thread/jsjvc2cqb91pyh47d4p6olk3c1vxqm3w] [2] [[DISCUSS] Conventions on assertions to use in tests|https://lists.apache.org/thread/33t7hz8w873p1bc5msppk65792z08rgt] [3] [JUnit5 migration guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] > Migration Flink from Junit4 to Junit5 > - > > Key: FLINK-25325 > URL: https://issues.apache.org/jira/browse/FLINK-25325 > Project: Flink > Issue Type: New Feature > Components: Tests >Affects Versions: 1.14.0 >Reporter: Jing Ge >Priority: Major > Labels: Umbrella > Fix For: 1.20.0 > > > Based on the consensus from the mailing list discussion[1][2], we have been > starting working on the JUnit4 to JUnit5 migration. > This is the umbrella ticket which describes the big picture of the migration > with following steps: > * AssertJ integration and guideline > * Test Framework upgrade from JUnit4 to JUnit5 > * JUnit5 migration guideline(document and reference migration) > * Optimization for issues found while writing new test in JUint5 > * [Long-term]Module based graceful migration of old tests in JUnit4 to JUnit5 > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > [https://github.com/apache/flink/pull/24483] is an excellent PR as example. > Please create similar Brief change log summary for new PR. > > [1] [[DISCUSS]Moving to > JUnit5|https://lists.apache.org/thread/jsjvc2cqb91pyh47d4p6olk3c1vxqm3w] > [2] [[DISCUSS] Conventions on assertions to use in > tests|https://lists.apache.org/thread/33t7hz8w873p1bc5msppk65792z08rgt] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-25352) Update stability annotations to include the since and missedGraduations fields
[
https://issues.apache.org/jira/browse/FLINK-25352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-25352:
---
Assignee: Jing Ge
> Update stability annotations to include the since and missedGraduations fields
> --
>
> Key: FLINK-25352
> URL: https://issues.apache.org/jira/browse/FLINK-25352
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.15.0
>Reporter: Till Rohrmann
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.20.0
>
>
> In order to implement the graduation process outlined in FLIP-197, we need to
> extend our stability annotations to include a {{since}} and
> {{missedGraduations}} fields.
> The idea of {{since}} is that it tells since when something has this
> stability guarantee.
> The idea of the {{missedGraduations}} field is to record reasons why an API
> has not been graduated.
> {code}
> @Target(ElementType.TYPE)
> public @interface PublicEvolving {
>
>FlinkVersion since();
>
>GraduationMiss[] missedGraduations();
> }
>
> public @interface GraduationMiss {
>FlinkVersion graduation();
>
>String reason();
> }
>
> // Usage
> @PublicEvolving(
>since = FlinkVersion.V1_11_0,
>missedGraduations = {
>@GraduationMiss(graduation = FlinkVersion.V1_13_0, reason =
> "foobar"),
>@GraduationMiss(graduation = FlinkVersion.V1_14_0, reason =
> "barfoo")
>})
> public class Foobar {}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34401) Translate "Flame Graphs" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-34401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-34401: Affects Version/s: 1.20.0 > Translate "Flame Graphs" page into Chinese > -- > > Key: FLINK-34401 > URL: https://issues.apache.org/jira/browse/FLINK-34401 > Project: Flink > Issue Type: Improvement > Components: chinese-translation >Affects Versions: 1.20.0 >Reporter: li you >Assignee: li you >Priority: Major > Labels: pull-request-available > > The page is located at _"docs/content.zh/docs/ops/debugging/flame_graphs.md"_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34401) Translate "Flame Graphs" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-34401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-34401: Fix Version/s: 1.20.0 > Translate "Flame Graphs" page into Chinese > -- > > Key: FLINK-34401 > URL: https://issues.apache.org/jira/browse/FLINK-34401 > Project: Flink > Issue Type: Improvement > Components: chinese-translation >Affects Versions: 1.20.0 >Reporter: li you >Assignee: li you >Priority: Major > Labels: pull-request-available > Fix For: 1.20.0 > > > The page is located at _"docs/content.zh/docs/ops/debugging/flame_graphs.md"_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FLINK-34401) Translate "Flame Graphs" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-34401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge closed FLINK-34401. --- Resolution: Fixed > Translate "Flame Graphs" page into Chinese > -- > > Key: FLINK-34401 > URL: https://issues.apache.org/jira/browse/FLINK-34401 > Project: Flink > Issue Type: Improvement > Components: chinese-translation >Affects Versions: 1.20.0 >Reporter: li you >Assignee: li you >Priority: Major > Labels: pull-request-available > Fix For: 1.20.0 > > > The page is located at _"docs/content.zh/docs/ops/debugging/flame_graphs.md"_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-34401) Translate "Flame Graphs" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-34401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34401: --- Assignee: li you > Translate "Flame Graphs" page into Chinese > -- > > Key: FLINK-34401 > URL: https://issues.apache.org/jira/browse/FLINK-34401 > Project: Flink > Issue Type: Improvement > Components: chinese-translation >Reporter: li you >Assignee: li you >Priority: Major > Labels: pull-request-available > > The page is located at _"docs/content.zh/docs/ops/debugging/flame_graphs.md"_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34401) Translate "Flame Graphs" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-34401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823962#comment-17823962 ] Jing Ge commented on FLINK-34401: - master: 76cce1e9d351eda4e76096707e1bc4302b200922 > Translate "Flame Graphs" page into Chinese > -- > > Key: FLINK-34401 > URL: https://issues.apache.org/jira/browse/FLINK-34401 > Project: Flink > Issue Type: Improvement > Components: chinese-translation >Reporter: li you >Priority: Major > Labels: pull-request-available > > The page is located at _"docs/content.zh/docs/ops/debugging/flame_graphs.md"_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34469) Implement TableDistribution toString
[ https://issues.apache.org/jira/browse/FLINK-34469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-34469: Affects Version/s: 1.20.0 > Implement TableDistribution toString > > > Key: FLINK-34469 > URL: https://issues.apache.org/jira/browse/FLINK-34469 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.20.0 >Reporter: Timo Walther >Assignee: Jeyhun Karimov >Priority: Minor > Labels: pull-request-available > Fix For: 1.20.0 > > > The newly added TableDistribution misses a toString implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34509) Docs: Fix Debezium JSON/AVRO opts in examples
[
https://issues.apache.org/jira/browse/FLINK-34509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-34509:
Fix Version/s: 1.20.0
> Docs: Fix Debezium JSON/AVRO opts in examples
> --
>
> Key: FLINK-34509
> URL: https://issues.apache.org/jira/browse/FLINK-34509
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Lorenzo Affetti
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.20.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Problem found here:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/formats/debezium/#how-to-use-debezium-format.]
> Here is the example provided:
> {code:java}
> CREATE TABLE topic_products (
> -- schema is totally the same to the MySQL "products" table
> id BIGINT,
> name STRING,
> description STRING,
> weight DECIMAL(10, 2)
> ) WITH (
> 'connector' = 'kafka',
> 'topic' = 'products_binlog',
> 'properties.bootstrap.servers' = 'localhost:9092',
> 'properties.group.id' = 'testGroup',
> -- using 'debezium-json' as the format to interpret Debezium JSON messages
> -- please use 'debezium-avro-confluent' if Debezium encodes messages in Avro
> format
> 'format' = 'debezium-json'
> ) {code}
> Actually, `debezium-json` would require `'debezium-json.schema-include' =
> 'true'` to work (as, by default, Debezium includes the schema. See
> [https://www.markhneedham.com/blog/2023/01/24/flink-sql-could-not-execute-sql-statement-corrupt-debezium-message/).]
> On the other hand `debezium-avro` would require the URL of the Confluent
> schema registry: `'debezium-avro-confluent.url' = '[http://...:8081'.]
> I propose to split the single example in 2 with the correct default options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34509) Docs: Fix Debezium JSON/AVRO opts in examples
[
https://issues.apache.org/jira/browse/FLINK-34509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-34509:
Affects Version/s: 1.19.0
1.20.0
> Docs: Fix Debezium JSON/AVRO opts in examples
> --
>
> Key: FLINK-34509
> URL: https://issues.apache.org/jira/browse/FLINK-34509
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Lorenzo Affetti
>Priority: Minor
> Labels: pull-request-available
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Problem found here:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/formats/debezium/#how-to-use-debezium-format.]
> Here is the example provided:
> {code:java}
> CREATE TABLE topic_products (
> -- schema is totally the same to the MySQL "products" table
> id BIGINT,
> name STRING,
> description STRING,
> weight DECIMAL(10, 2)
> ) WITH (
> 'connector' = 'kafka',
> 'topic' = 'products_binlog',
> 'properties.bootstrap.servers' = 'localhost:9092',
> 'properties.group.id' = 'testGroup',
> -- using 'debezium-json' as the format to interpret Debezium JSON messages
> -- please use 'debezium-avro-confluent' if Debezium encodes messages in Avro
> format
> 'format' = 'debezium-json'
> ) {code}
> Actually, `debezium-json` would require `'debezium-json.schema-include' =
> 'true'` to work (as, by default, Debezium includes the schema. See
> [https://www.markhneedham.com/blog/2023/01/24/flink-sql-could-not-execute-sql-statement-corrupt-debezium-message/).]
> On the other hand `debezium-avro` would require the URL of the Confluent
> schema registry: `'debezium-avro-confluent.url' = '[http://...:8081'.]
> I propose to split the single example in 2 with the correct default options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FLINK-34509) Docs: Fix Debezium JSON/AVRO opts in examples
[
https://issues.apache.org/jira/browse/FLINK-34509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge closed FLINK-34509.
---
Resolution: Fixed
> Docs: Fix Debezium JSON/AVRO opts in examples
> --
>
> Key: FLINK-34509
> URL: https://issues.apache.org/jira/browse/FLINK-34509
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Lorenzo Affetti
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.20.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Problem found here:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/formats/debezium/#how-to-use-debezium-format.]
> Here is the example provided:
> {code:java}
> CREATE TABLE topic_products (
> -- schema is totally the same to the MySQL "products" table
> id BIGINT,
> name STRING,
> description STRING,
> weight DECIMAL(10, 2)
> ) WITH (
> 'connector' = 'kafka',
> 'topic' = 'products_binlog',
> 'properties.bootstrap.servers' = 'localhost:9092',
> 'properties.group.id' = 'testGroup',
> -- using 'debezium-json' as the format to interpret Debezium JSON messages
> -- please use 'debezium-avro-confluent' if Debezium encodes messages in Avro
> format
> 'format' = 'debezium-json'
> ) {code}
> Actually, `debezium-json` would require `'debezium-json.schema-include' =
> 'true'` to work (as, by default, Debezium includes the schema. See
> [https://www.markhneedham.com/blog/2023/01/24/flink-sql-could-not-execute-sql-statement-corrupt-debezium-message/).]
> On the other hand `debezium-avro` would require the URL of the Confluent
> schema registry: `'debezium-avro-confluent.url' = '[http://...:8081'.]
> I propose to split the single example in 2 with the correct default options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34509) Docs: Fix Debezium JSON/AVRO opts in examples
[
https://issues.apache.org/jira/browse/FLINK-34509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823793#comment-17823793
]
Jing Ge commented on FLINK-34509:
-
master: 641f4f4d0d0156b84bdb9ba528b1dd96f7ae9d9c
> Docs: Fix Debezium JSON/AVRO opts in examples
> --
>
> Key: FLINK-34509
> URL: https://issues.apache.org/jira/browse/FLINK-34509
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Reporter: Lorenzo Affetti
>Priority: Minor
> Labels: pull-request-available
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Problem found here:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/formats/debezium/#how-to-use-debezium-format.]
> Here is the example provided:
> {code:java}
> CREATE TABLE topic_products (
> -- schema is totally the same to the MySQL "products" table
> id BIGINT,
> name STRING,
> description STRING,
> weight DECIMAL(10, 2)
> ) WITH (
> 'connector' = 'kafka',
> 'topic' = 'products_binlog',
> 'properties.bootstrap.servers' = 'localhost:9092',
> 'properties.group.id' = 'testGroup',
> -- using 'debezium-json' as the format to interpret Debezium JSON messages
> -- please use 'debezium-avro-confluent' if Debezium encodes messages in Avro
> format
> 'format' = 'debezium-json'
> ) {code}
> Actually, `debezium-json` would require `'debezium-json.schema-include' =
> 'true'` to work (as, by default, Debezium includes the schema. See
> [https://www.markhneedham.com/blog/2023/01/24/flink-sql-could-not-execute-sql-statement-corrupt-debezium-message/).]
> On the other hand `debezium-avro` would require the URL of the Confluent
> schema registry: `'debezium-avro-confluent.url' = '[http://...:8081'.]
> I propose to split the single example in 2 with the correct default options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34571) SortMergeResultPartitionReadSchedulerTest.testOnReadBufferRequestError failed due an assertion
[
https://issues.apache.org/jira/browse/FLINK-34571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34571:
---
Assignee: Weijie Guo
> SortMergeResultPartitionReadSchedulerTest.testOnReadBufferRequestError failed
> due an assertion
> --
>
> Key: FLINK-34571
> URL: https://issues.apache.org/jira/browse/FLINK-34571
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Network
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Matthias Pohl
>Assignee: Weijie Guo
>Priority: Critical
> Labels: github-actions, test-stability
>
> https://github.com/apache/flink/actions/runs/8134965216/job/8875618#step:10:8586
> {code}
> Error: 02:39:36 02:39:36.688 [ERROR] Tests run: 9, Failures: 1, Errors: 0,
> Skipped: 0, Time elapsed: 13.68 s <<< FAILURE! -- in
> org.apache.flink.runtime.io.network.partition.SortMergeResultPartitionReadSchedulerTest
> Error: 02:39:36 02:39:36.689 [ERROR]
> org.apache.flink.runtime.io.network.partition.SortMergeResultPartitionReadSchedulerTest.testOnReadBufferRequestError
> -- Time elapsed: 0.174 s <<< FAILURE!
> Mar 04 02:39:36 org.opentest4j.AssertionFailedError:
> Mar 04 02:39:36
> Mar 04 02:39:36 Expecting value to be true but was false
> Mar 04 02:39:36 at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> Mar 04 02:39:36 at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> Mar 04 02:39:36 at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> Mar 04 02:39:36 at
> org.apache.flink.runtime.io.network.partition.SortMergeResultPartitionReadSchedulerTest.testOnReadBufferRequestError(SortMergeResultPartitionReadSchedulerTest.java:225)
> Mar 04 02:39:36 at java.lang.reflect.Method.invoke(Method.java:498)
> Mar 04 02:39:36 at
> java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:189)
> Mar 04 02:39:36 at
> java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> Mar 04 02:39:36 at
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> Mar 04 02:39:36 at
> java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> Mar 04 02:39:36 at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34111) Add JSON_QUOTE and JSON_UNQUOTE function
[ https://issues.apache.org/jira/browse/FLINK-34111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34111: --- Assignee: Jeyhun Karimov > Add JSON_QUOTE and JSON_UNQUOTE function > > > Key: FLINK-34111 > URL: https://issues.apache.org/jira/browse/FLINK-34111 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Reporter: Martijn Visser >Assignee: Jeyhun Karimov >Priority: Major > Labels: pull-request-available > > Escapes or unescapes a JSON string removing traces of offending characters > that could prevent parsing. > Proposal: > - JSON_QUOTE: Quotes a string by wrapping it with double quote characters and > escaping interior quote and other characters, then returning the result as a > utf8mb4 string. Returns NULL if the argument is NULL. > - JSON_UNQUOTE: Unquotes value and returns the result as a string. Returns > NULL if the argument is NULL. An error occurs if the value starts and ends > with double quotes but is not a valid JSON string literal. > The following characters are reserved in JSON and must be properly escaped to > be used in strings: > Backspace is replaced with \b > Form feed is replaced with \f > Newline is replaced with \n > Carriage return is replaced with \r > Tab is replaced with \t > Double quote is replaced with \" > Backslash is replaced with \\ > This function exists in MySQL: > - > https://dev.mysql.com/doc/refman/8.0/en/json-creation-functions.html#function_json-quote > - > https://dev.mysql.com/doc/refman/8.0/en/json-modification-functions.html#function_json-unquote > It's still open in Calcite CALCITE-3130 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-34366) Add support to group rows by column ordinals
[
https://issues.apache.org/jira/browse/FLINK-34366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34366:
---
Assignee: Jeyhun Karimov
> Add support to group rows by column ordinals
>
>
> Key: FLINK-34366
> URL: https://issues.apache.org/jira/browse/FLINK-34366
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
>Reporter: Martijn Visser
>Assignee: Jeyhun Karimov
>Priority: Major
> Labels: pull-request-available
>
> Reference: BigQuery
> https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#group_by_col_ordinals
> The GROUP BY clause can refer to expression names in the SELECT list. The
> GROUP BY clause also allows ordinal references to expressions in the SELECT
> list, using integer values. 1 refers to the first value in the SELECT list, 2
> the second, and so forth. The value list can combine ordinals and value
> names. The following queries are equivalent:
> {code:sql}
> WITH PlayerStats AS (
> SELECT 'Adams' as LastName, 'Noam' as FirstName, 3 as PointsScored UNION ALL
> SELECT 'Buchanan', 'Jie', 0 UNION ALL
> SELECT 'Coolidge', 'Kiran', 1 UNION ALL
> SELECT 'Adams', 'Noam', 4 UNION ALL
> SELECT 'Buchanan', 'Jie', 13)
> SELECT SUM(PointsScored) AS total_points, LastName, FirstName
> FROM PlayerStats
> GROUP BY LastName, FirstName;
> /*--+--+---+
> | total_points | LastName | FirstName |
> +--+--+---+
> | 7| Adams| Noam |
> | 13 | Buchanan | Jie |
> | 1| Coolidge | Kiran |
> +--+--+---*/
> {code}
> {code:sql}
> WITH PlayerStats AS (
> SELECT 'Adams' as LastName, 'Noam' as FirstName, 3 as PointsScored UNION ALL
> SELECT 'Buchanan', 'Jie', 0 UNION ALL
> SELECT 'Coolidge', 'Kiran', 1 UNION ALL
> SELECT 'Adams', 'Noam', 4 UNION ALL
> SELECT 'Buchanan', 'Jie', 13)
> SELECT SUM(PointsScored) AS total_points, LastName, FirstName
> FROM PlayerStats
> GROUP BY 2, 3;
> /*--+--+---+
> | total_points | LastName | FirstName |
> +--+--+---+
> | 7| Adams| Noam |
> | 13 | Buchanan | Jie |
> | 1| Coolidge | Kiran |
> +--+--+---*/
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34477) support capture groups in REGEXP_REPLACE
[
https://issues.apache.org/jira/browse/FLINK-34477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34477:
---
Assignee: Jeyhun Karimov
> support capture groups in REGEXP_REPLACE
>
>
> Key: FLINK-34477
> URL: https://issues.apache.org/jira/browse/FLINK-34477
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
>Affects Versions: 1.18.1
>Reporter: David Anderson
>Assignee: Jeyhun Karimov
>Priority: Major
> Labels: pull-request-available
>
> For example, I would expect this query
> {code:java}
> select REGEXP_REPLACE('ERR1,ERR2', '([^,]+)', 'AA$1AA'); {code}
> to produce
> {code:java}
> AAERR1AA,AAERR2AA{code}
> but instead it produces
> {code:java}
> AA$1AA,AA$1AA{code}
> With FLINK-9990 support was added for REGEXP_EXTRACT, which does provide
> access to the capture groups, but for many use cases supporting this in the
> way that users expect, in REGEXP_REPLACE, would be more natural and
> convenient.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FLINK-34469) Implement TableDistribution toString
[ https://issues.apache.org/jira/browse/FLINK-34469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge closed FLINK-34469. --- Resolution: Fixed > Implement TableDistribution toString > > > Key: FLINK-34469 > URL: https://issues.apache.org/jira/browse/FLINK-34469 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Reporter: Timo Walther >Assignee: Jeyhun Karimov >Priority: Minor > Labels: pull-request-available > Fix For: 1.20.0 > > > The newly added TableDistribution misses a toString implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34469) Implement TableDistribution toString
[ https://issues.apache.org/jira/browse/FLINK-34469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-34469: Fix Version/s: 1.20.0 > Implement TableDistribution toString > > > Key: FLINK-34469 > URL: https://issues.apache.org/jira/browse/FLINK-34469 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Reporter: Timo Walther >Assignee: Jeyhun Karimov >Priority: Minor > Labels: pull-request-available > Fix For: 1.20.0 > > > The newly added TableDistribution misses a toString implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-34469) Implement TableDistribution toString
[ https://issues.apache.org/jira/browse/FLINK-34469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34469: --- Assignee: Jeyhun Karimov > Implement TableDistribution toString > > > Key: FLINK-34469 > URL: https://issues.apache.org/jira/browse/FLINK-34469 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Reporter: Timo Walther >Assignee: Jeyhun Karimov >Priority: Minor > Labels: pull-request-available > > The newly added TableDistribution misses a toString implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34469) Implement TableDistribution toString
[ https://issues.apache.org/jira/browse/FLINK-34469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823004#comment-17823004 ] Jing Ge commented on FLINK-34469: - master: 322a841694968b5b8f7bb7c6cd9dd85d9d17e23f > Implement TableDistribution toString > > > Key: FLINK-34469 > URL: https://issues.apache.org/jira/browse/FLINK-34469 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Reporter: Timo Walther >Priority: Minor > Labels: pull-request-available > > The newly added TableDistribution misses a toString implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-20399) Migrate test_sql_client.sh
[ https://issues.apache.org/jira/browse/FLINK-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-20399: --- Assignee: Lorenzo Affetti > Migrate test_sql_client.sh > -- > > Key: FLINK-20399 > URL: https://issues.apache.org/jira/browse/FLINK-20399 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API, Table SQL / Client, Tests >Reporter: Jark Wu >Assignee: Lorenzo Affetti >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-20398) Migrate test_batch_sql.sh
[ https://issues.apache.org/jira/browse/FLINK-20398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-20398: --- Assignee: Lorenzo Affetti > Migrate test_batch_sql.sh > - > > Key: FLINK-20398 > URL: https://issues.apache.org/jira/browse/FLINK-20398 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API, Tests >Reporter: Jark Wu >Assignee: Lorenzo Affetti >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34202) python tests take suspiciously long in some of the cases
[ https://issues.apache.org/jira/browse/FLINK-34202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818693#comment-17818693 ] Jing Ge edited comment on FLINK-34202 at 2/20/24 8:04 AM: -- Thanks for the info, [~lorenzo.affetti] could you please help check the Alibaba001 VM? was (Author: jingge): Thanks for the info, [~lorenzo.affetti] could you help check the Alibaba001 VM? > python tests take suspiciously long in some of the cases > > > Key: FLINK-34202 > URL: https://issues.apache.org/jira/browse/FLINK-34202 > Project: Flink > Issue Type: Bug > Components: API / Python >Affects Versions: 1.17.2, 1.19.0, 1.18.1 >Reporter: Matthias Pohl >Assignee: Xingbo Huang >Priority: Critical > Labels: pull-request-available, test-stability > > [This release-1.18 > build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603=logs=3e4dd1a2-fe2f-5e5d-a581-48087e718d53=b4612f28-e3b5-5853-8a8b-610ae894217a] > has the python stage running into a timeout without any obvious reason. The > [python stage run for > JDK17|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603=logs=b53e1644-5cb4-5a3b-5d48-f523f39bcf06] > was also getting close to the 4h timeout. > I'm creating this issue for documentation purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34202) python tests take suspiciously long in some of the cases
[ https://issues.apache.org/jira/browse/FLINK-34202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818693#comment-17818693 ] Jing Ge edited comment on FLINK-34202 at 2/20/24 8:01 AM: -- Thanks for the info, [~lorenzo.affetti] could you help check the Alibaba001 VM? was (Author: jingge): Thanks for the info, [~jeyhunkarimov] could you help check the Alibaba001 VM? > python tests take suspiciously long in some of the cases > > > Key: FLINK-34202 > URL: https://issues.apache.org/jira/browse/FLINK-34202 > Project: Flink > Issue Type: Bug > Components: API / Python >Affects Versions: 1.17.2, 1.19.0, 1.18.1 >Reporter: Matthias Pohl >Assignee: Xingbo Huang >Priority: Critical > Labels: pull-request-available, test-stability > > [This release-1.18 > build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603=logs=3e4dd1a2-fe2f-5e5d-a581-48087e718d53=b4612f28-e3b5-5853-8a8b-610ae894217a] > has the python stage running into a timeout without any obvious reason. The > [python stage run for > JDK17|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603=logs=b53e1644-5cb4-5a3b-5d48-f523f39bcf06] > was also getting close to the 4h timeout. > I'm creating this issue for documentation purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34202) python tests take suspiciously long in some of the cases
[ https://issues.apache.org/jira/browse/FLINK-34202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818693#comment-17818693 ] Jing Ge commented on FLINK-34202: - Thanks for the info, [~jeyhunkarimov] could you help check the Alibaba001 VM? > python tests take suspiciously long in some of the cases > > > Key: FLINK-34202 > URL: https://issues.apache.org/jira/browse/FLINK-34202 > Project: Flink > Issue Type: Bug > Components: API / Python >Affects Versions: 1.17.2, 1.19.0, 1.18.1 >Reporter: Matthias Pohl >Assignee: Xingbo Huang >Priority: Critical > Labels: pull-request-available, test-stability > > [This release-1.18 > build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603=logs=3e4dd1a2-fe2f-5e5d-a581-48087e718d53=b4612f28-e3b5-5853-8a8b-610ae894217a] > has the python stage running into a timeout without any obvious reason. The > [python stage run for > JDK17|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603=logs=b53e1644-5cb4-5a3b-5d48-f523f39bcf06] > was also getting close to the 4h timeout. > I'm creating this issue for documentation purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34446) SqlValidatorException with LATERAL TABLE and JOIN
[
https://issues.apache.org/jira/browse/FLINK-34446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818466#comment-17818466
]
Jing Ge commented on FLINK-34446:
-
Let's wait until the PR [https://github.com/apache/calcite/pull/3690] has been
reviewed and is accepted.
> SqlValidatorException with LATERAL TABLE and JOIN
> -
>
> Key: FLINK-34446
> URL: https://issues.apache.org/jira/browse/FLINK-34446
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Ecosystem, Table SQL / Planner
>Reporter: Jing Ge
>Assignee: Jeyhun Karimov
>Priority: Critical
> Labels: pull-request-available
>
> found one regression issue. Query working Flink 1.17.2, but failing with
> Flink 1.18.+
>
> {code:java}
> -- Query working Flink 1.17.2, but failing with Flink 1.18.+
> -- -- [ERROR] Could not execute SQL statement. Reason:
> -- -- org.apache.calcite.sql.validate.SqlValidatorException: Table 's' not
> found
> SELECT * FROM sample as s,
> LATERAL TABLE(split(s.id,'[01]'))
> CROSS JOIN (VALUES ('A'), ('B'));
> {code}
> The problem is not related to the the alias scope. Even if we replace
> split(s.id.. ) with split(id,...) the error
> {code:java}
> Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Column 'id'
> not found in any table
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> {code}
> will be generated. This seems to be Calcite issue, since this test fails on
> Calcite v1.32 and does not fail on Calcite 1.29.0 and 1.30.0.
> We tested it with Calcite versions 1.31.0, 1.32.0, 1.33.0, 1.34.0, 1.35.0,
> 1.36.0 and the main branch (c774c313a81d01c4e3e77cf296d04839c5ab04c0). The
> issue still remains
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-31362) Upgrade to Calcite version to 1.33.0
[ https://issues.apache.org/jira/browse/FLINK-31362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817728#comment-17817728 ] Jing Ge commented on FLINK-31362: - Thanks for the clarification. > Upgrade to Calcite version to 1.33.0 > > > Key: FLINK-31362 > URL: https://issues.apache.org/jira/browse/FLINK-31362 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: WenJun Min >Assignee: Sergey Nuyanzin >Priority: Major > Labels: pull-request-available > > In Calcite 1.33.0, C-style escape strings have been supported. We could > leverage it to enhance our string literals usage. > issue: https://issues.apache.org/jira/browse/CALCITE-5305 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-31362) Upgrade to Calcite version to 1.33.0
[ https://issues.apache.org/jira/browse/FLINK-31362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817711#comment-17817711 ] Jing Ge edited comment on FLINK-31362 at 2/15/24 3:47 PM: -- Hi folks, would you like to share the reason why we should upgrade to 1.33.0 instead of the most up-to-date 1.36.0? A critical issue has been found FLINK-34446. We should consider: # downgrade to 1.30.0 # fix the issue in Calcite # wait for the next Calcite release # upgrade to Calcite e.g. 1.37.0 [~Sergey Nuyanzin] do you have any concerns? was (Author: jingge): Hi folks, would you like to share the reason why we should upgrade to 1.33.0 instead of the most up-to-date version? A critical issue has been found FLINK-34446. We should consider: # downgrade to 1.30.0 # fix the issue in Calcite # wait for the next Calcite release # upgrade to Calcite e.g. 1.37.0 [~Sergey Nuyanzin] do you have any concerns? > Upgrade to Calcite version to 1.33.0 > > > Key: FLINK-31362 > URL: https://issues.apache.org/jira/browse/FLINK-31362 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: WenJun Min >Assignee: Sergey Nuyanzin >Priority: Major > Labels: pull-request-available > > In Calcite 1.33.0, C-style escape strings have been supported. We could > leverage it to enhance our string literals usage. > issue: https://issues.apache.org/jira/browse/CALCITE-5305 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-31362) Upgrade to Calcite version to 1.33.0
[ https://issues.apache.org/jira/browse/FLINK-31362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817711#comment-17817711 ] Jing Ge edited comment on FLINK-31362 at 2/15/24 3:35 PM: -- Hi folks, would you like to share the reason why we should upgrade to 1.33.0 instead of the most up-to-date version? A critical issue has been found FLINK-34446. We should consider: # downgrade to 1.30.0 # fix the issue in Calcite # wait for the next Calcite release # upgrade to Calcite e.g. 1.37.0 [~Sergey Nuyanzin] do you have any concerns? was (Author: jingge): Hi folks, would you like share the reason why we should upgrade to 1.33.0 instead of the most up-to-date version? A critical issue has been found FLINK-34446. We should consider: # downgrade to 1.30.0 # fix the issue in Calcite # wait for the next Calcite release # upgrade to Calcite e.g. 1.37.0 > Upgrade to Calcite version to 1.33.0 > > > Key: FLINK-31362 > URL: https://issues.apache.org/jira/browse/FLINK-31362 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: WenJun Min >Assignee: Sergey Nuyanzin >Priority: Major > Labels: pull-request-available > > In Calcite 1.33.0, C-style escape strings have been supported. We could > leverage it to enhance our string literals usage. > issue: https://issues.apache.org/jira/browse/CALCITE-5305 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-31362) Upgrade to Calcite version to 1.33.0
[ https://issues.apache.org/jira/browse/FLINK-31362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817711#comment-17817711 ] Jing Ge commented on FLINK-31362: - Hi folks, would you like share the reason why we should upgrade to 1.33.0 instead of the most up-to-date version? A critical issue has been found FLINK-34446. We should consider: # downgrade to 1.30.0 # fix the issue in Calcite # wait for the next Calcite release # upgrade to Calcite e.g. 1.37.0 > Upgrade to Calcite version to 1.33.0 > > > Key: FLINK-31362 > URL: https://issues.apache.org/jira/browse/FLINK-31362 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: WenJun Min >Assignee: Sergey Nuyanzin >Priority: Major > Labels: pull-request-available > > In Calcite 1.33.0, C-style escape strings have been supported. We could > leverage it to enhance our string literals usage. > issue: https://issues.apache.org/jira/browse/CALCITE-5305 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34446) regression: alias is not supported in lateral join with UDF
[
https://issues.apache.org/jira/browse/FLINK-34446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-34446:
Summary: regression: alias is not supported in lateral join with UDF (was:
regression: alias is not supportedin lateral join)
> regression: alias is not supported in lateral join with UDF
> ---
>
> Key: FLINK-34446
> URL: https://issues.apache.org/jira/browse/FLINK-34446
> Project: Flink
> Issue Type: Bug
>Reporter: Jing Ge
>Assignee: Jeyhun Karimov
>Priority: Critical
>
> found one regression issue. Query working Flink 1.17.2, but failing with
> Flink 1.18.+
>
> {code:java}
> -- Query working Flink 1.17.2, but failing with Flink 1.18.+
> -- -- [ERROR] Could not execute SQL statement. Reason:
> -- -- org.apache.calcite.sql.validate.SqlValidatorException: Table 's' not
> found
> SELECT * FROM sample as s,
> LATERAL TABLE(split(s.id,'[01]'))
> CROSS JOIN (VALUES ('A'), ('B'));
> {code}
> The problem is not related to the the alias scope. Even if we replace
> split(s.id.. ) with split(id,...) the error
> {code:java}
> Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Column 'id'
> not found in any table
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> {code}
> will be generated. This seems to be Calcite issue, since this test fails on
> Calcite v1.32 and does not fail on Calcite v1.29.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34446) regression: alias is not supportedin lateral join
[
https://issues.apache.org/jira/browse/FLINK-34446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-34446:
Summary: regression: alias is not supportedin lateral join (was:
SqlValidatorException with Lateral Table and CROSS JOIN)
> regression: alias is not supportedin lateral join
> -
>
> Key: FLINK-34446
> URL: https://issues.apache.org/jira/browse/FLINK-34446
> Project: Flink
> Issue Type: Bug
>Reporter: Jing Ge
>Assignee: Jeyhun Karimov
>Priority: Critical
>
> found one regression issue. Query working Flink 1.17.2, but failing with
> Flink 1.18.+
>
> {code:java}
> -- Query working Flink 1.17.2, but failing with Flink 1.18.+
> -- -- [ERROR] Could not execute SQL statement. Reason:
> -- -- org.apache.calcite.sql.validate.SqlValidatorException: Table 's' not
> found
> SELECT * FROM sample as s,
> LATERAL TABLE(split(s.id,'[01]'))
> CROSS JOIN (VALUES ('A'), ('B'));
> {code}
> The problem is not related to the the alias scope. Even if we replace
> split(s.id.. ) with split(id,...) the error
> {code:java}
> Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Column 'id'
> not found in any table
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> {code}
> will be generated. This seems to be Calcite issue, since this test fails on
> Calcite v1.32 and does not fail on Calcite v1.29.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34446) regression: alias is not in lateral join
[
https://issues.apache.org/jira/browse/FLINK-34446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34446:
---
Assignee: Jeyhun Karimov
> regression: alias is not in lateral join
>
>
> Key: FLINK-34446
> URL: https://issues.apache.org/jira/browse/FLINK-34446
> Project: Flink
> Issue Type: Bug
>Reporter: Jing Ge
>Assignee: Jeyhun Karimov
>Priority: Critical
>
> found one regression issue. Query working Flink 1.17.2, but failing with
> Flink 1.18.+
>
> {code:java}
> -- Query working Flink 1.17.2, but failing with Flink 1.18.+
> -- -- [ERROR] Could not execute SQL statement. Reason:
> -- -- org.apache.calcite.sql.validate.SqlValidatorException: Table 's' not
> found
> SELECT
> a_or_b,
> id,
> splits
> FROM sample as s ,
> LATERAL TABLE(split(s.id,'[01]')) lt(splits)
> CROSS JOIN (VALUES ('A'), ('B')) AS cj(a_or_b); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-34446) regression: alias is not in lateral join
Jing Ge created FLINK-34446:
---
Summary: regression: alias is not in lateral join
Key: FLINK-34446
URL: https://issues.apache.org/jira/browse/FLINK-34446
Project: Flink
Issue Type: Bug
Reporter: Jing Ge
found one regression issue. Query working Flink 1.17.2, but failing with Flink
1.18.+
{code:java}
-- Query working Flink 1.17.2, but failing with Flink 1.18.+
-- -- [ERROR] Could not execute SQL statement. Reason:
-- -- org.apache.calcite.sql.validate.SqlValidatorException: Table 's' not found
SELECT
a_or_b,
id,
splits
FROM sample as s ,
LATERAL TABLE(split(s.id,'[01]')) lt(splits)
CROSS JOIN (VALUES ('A'), ('B')) AS cj(a_or_b); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34442) Support optimizations for pre-partitioned [external] data sources
[ https://issues.apache.org/jira/browse/FLINK-34442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34442: --- Assignee: Jeyhun Karimov > Support optimizations for pre-partitioned [external] data sources > - > > Key: FLINK-34442 > URL: https://issues.apache.org/jira/browse/FLINK-34442 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API, Table SQL / Planner >Affects Versions: 1.18.1 >Reporter: Jeyhun Karimov >Assignee: Jeyhun Karimov >Priority: Major > > There are some use-cases in which data sources are pre-partitioned: > - Kafka broker is already partitioned w.r.t. some key[s] > - There are multiple [Flink] jobs that materialize their outputs and read > them as input subsequently > One of the main benefits is that we might avoid unnecessary shuffling. > There is already an experimental feature in DataStream to support a subset of > these [1]. > We should support this for Flink Table/SQL as well. > [1] > https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/experimental/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34282) Create a release branch
[
https://issues.apache.org/jira/browse/FLINK-34282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816910#comment-17816910
]
Jing Ge commented on FLINK-34282:
-
[AzureCI project
configuration|https://dev.azure.com/apache-flink/apache-flink/]:
# go to flink-ci.flink-master-mirror
# click Edit
# click More Actions(three dots)
# click Triggers
# click 0:15 under scheduled
# add refs/heads/release-1.19 into the branch filters
# remove refs/heads/release-1.16
> Create a release branch
> ---
>
> Key: FLINK-34282
> URL: https://issues.apache.org/jira/browse/FLINK-34282
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.19.0
>Reporter: lincoln lee
>Assignee: lincoln lee
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
> Attachments: screenshot-1.png
>
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
> h4. Flink repository
> Create a branch for the new version that we want to release before updating
> the master branch to the next development version:
> {code:bash}
> $ cd ./tools
> tools $ releasing/create_snapshot_branch.sh
> tools $ git checkout master
> tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION
> NEW_VERSION=$NEXT_SNAPSHOT_VERSION releasing/update_branch_version.sh
> {code}
> In the {{master}} branch, add a new value (e.g. {{v1_16("1.16")}}) to
> [apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
> as the last entry:
> {code:java}
> // ...
> v1_12("1.12"),
> v1_13("1.13"),
> v1_14("1.14"),
> v1_15("1.15"),
> v1_16("1.16");
> {code}
> Additionally in master, update the branch list of the GitHub Actions nightly
> workflow (see
> [apache/flink:.github/workflows/nightly-trigger.yml#L31ff|https://github.com/apache/flink/blob/master/.github/workflows/nightly-trigger.yml#L31]):
> The two most-recent releases and master should be covered.
> The newly created branch and updated {{master}} branch need to be pushed to
> the official repository.
> h4. Flink Docker Repository
> Afterwards fork off from {{dev-master}} a {{dev-x.y}} branch in the
> [apache/flink-docker|https://github.com/apache/flink-docker] repository. Make
> sure that
> [apache/flink-docker:.github/workflows/ci.yml|https://github.com/apache/flink-docker/blob/dev-master/.github/workflows/ci.yml]
> points to the correct snapshot version; for {{dev-x.y}} it should point to
> {{{}x.y-SNAPSHOT{}}}, while for {{dev-master}} it should point to the most
> recent snapshot version (\{[$NEXT_SNAPSHOT_VERSION}}).
> After pushing the new minor release branch, as the last step you should also
> update the documentation workflow to also build the documentation for the new
> release branch. Check [Managing
> Documentation|https://cwiki.apache.org/confluence/display/FLINK/Managing+Documentation]
> on details on how to do that. You may also want to manually trigger a build
> to make the changes visible as soon as possible.
> h4. Flink Benchmark Repository
> First of all, checkout the {{master}} branch to {{dev-x.y}} branch in
> [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks], so that
> we can have a branch named {{dev-x.y}} which could be built on top of
> (${{CURRENT_SNAPSHOT_VERSION}}).
> Then, inside the repository you need to manually update the {{flink.version}}
> property inside the parent *pom.xml* file. It should be pointing to the most
> recent snapshot version ($NEXT_SNAPSHOT_VERSION). For example:
> {code:xml}
> 1.18-SNAPSHOT
> {code}
> h4. AzureCI Project Configuration
> The new release branch needs to be configured within AzureCI to make azure
> aware of the new release branch. This matter can only be handled by Ververica
> employees since they are owning the AzureCI setup.
>
>
> h3. Expectations (Minor Version only if not stated otherwise)
> * Release branch has been created and pushed
> * Changes on the new release branch are picked up by [Azure
> CI|https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary]
> * {{master}} branch has the version information updated to the new version
> (check pom.xml files and
> *
>
[jira] [Closed] (FLINK-34367) Release Testing Instructions: Verify FLINK-34027 AsyncScalarFunction for asynchronous scalar function support
[ https://issues.apache.org/jira/browse/FLINK-34367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge closed FLINK-34367. --- Resolution: Fixed > Release Testing Instructions: Verify FLINK-34027 AsyncScalarFunction for > asynchronous scalar function support > - > > Key: FLINK-34367 > URL: https://issues.apache.org/jira/browse/FLINK-34367 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Alan Sheinberg >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34273) git fetch fails
[
https://issues.apache.org/jira/browse/FLINK-34273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-34273:
Priority: Major (was: Critical)
> git fetch fails
> ---
>
> Key: FLINK-34273
> URL: https://issues.apache.org/jira/browse/FLINK-34273
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI, Test Infrastructure
>Affects Versions: 1.19.0, 1.18.1
>Reporter: Matthias Pohl
>Priority: Major
> Labels: test-stability
>
> We've seen multiple {{git fetch}} failures. I assume this to be an
> infrastructure issue. This Jira issue is for documentation purposes.
> {code:java}
> error: RPC failed; curl 18 transfer closed with outstanding read data
> remaining
> error: 5211 bytes of body are still expected
> fetch-pack: unexpected disconnect while reading sideband packet
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack output {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57080=logs=0e7be18f-84f2-53f0-a32d-4a5e4a174679=5d6dc3d3-393d-5111-3a40-c6a5a36202e6=667
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34427) ResourceManagerTaskExecutorTest fails fatally (exit code 239)
[
https://issues.apache.org/jira/browse/FLINK-34427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34427:
---
Assignee: Matthias Pohl
> ResourceManagerTaskExecutorTest fails fatally (exit code 239)
> -
>
> Key: FLINK-34427
> URL: https://issues.apache.org/jira/browse/FLINK-34427
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Matthias Pohl
>Assignee: Matthias Pohl
>Priority: Critical
> Labels: test-stability
>
> https://github.com/apache/flink/actions/runs/7866453350/job/21460921911#step:10:8959
> {code}
> Error: 02:28:53 02:28:53.220 [ERROR] Process Exit Code: 239
> Error: 02:28:53 02:28:53.220 [ERROR] Crashed tests:
> Error: 02:28:53 02:28:53.220 [ERROR]
> org.apache.flink.runtime.resourcemanager.ResourceManagerTaskExecutorTest
> Error: 02:28:53 02:28:53.220 [ERROR]
> org.apache.maven.surefire.booter.SurefireBooterForkException:
> ExecutionException The forked VM terminated without properly saying goodbye.
> VM crash or System.exit called?
> Error: 02:28:53 02:28:53.220 [ERROR] Command was /bin/sh -c cd
> '/root/flink/flink-runtime' &&
> '/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java' '-XX:+UseG1GC' '-Xms256m'
> '-XX:+IgnoreUnrecognizedVMOptions'
> '--add-opens=java.base/java.util=ALL-UNNAMED'
> '--add-opens=java.base/java.lang=ALL-UNNAMED'
> '--add-opens=java.base/java.net=ALL-UNNAMED'
> '--add-opens=java.base/java.io=ALL-UNNAMED'
> '--add-opens=java.base/java.util.concurrent=ALL-UNNAMED' '-Xmx768m' '-jar'
> '/root/flink/flink-runtime/target/surefire/surefirebooter-20240212022332296_94.jar'
> '/root/flink/flink-runtime/target/surefire'
> '2024-02-12T02-21-39_495-jvmRun3' 'surefire-20240212022332296_88tmp'
> 'surefire_26-20240212022332296_91tmp'
> Error: 02:28:53 02:28:53.220 [ERROR] Error occurred in starting fork, check
> output in log
> Error: 02:28:53 02:28:53.220 [ERROR] Process Exit Code: 239
> Error: 02:28:53 02:28:53.220 [ERROR] Crashed tests:
> Error: 02:28:53 02:28:53.221 [ERROR]
> org.apache.flink.runtime.resourcemanager.ResourceManagerTaskExecutorTest
> Error: 02:28:53 02:28:53.221 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:456)
> [...]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34425) TaskManagerRunnerITCase#testNondeterministicWorkingDirIsDeletedInCaseOfProcessFailure times out
[
https://issues.apache.org/jira/browse/FLINK-34425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34425:
---
Assignee: Matthias Pohl
> TaskManagerRunnerITCase#testNondeterministicWorkingDirIsDeletedInCaseOfProcessFailure
> times out
> ---
>
> Key: FLINK-34425
> URL: https://issues.apache.org/jira/browse/FLINK-34425
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Matthias Pohl
>Assignee: Matthias Pohl
>Priority: Critical
> Labels: test-stability
>
> https://github.com/apache/flink/actions/runs/7851900616/job/21429757962#step:10:8844
> {code}
> Feb 10 03:21:45 "main" #1 [498632] prio=5 os_prio=0 cpu=619.91ms
> elapsed=1653.40s tid=0x7fbd29695000 nid=498632 waiting on condition
> [0x7fbd2b9f3000]
> Feb 10 03:21:45java.lang.Thread.State: WAITING (parking)
> Feb 10 03:21:45 at
> jdk.internal.misc.Unsafe.park(java.base@21.0.1/Native Method)
> Feb 10 03:21:45 - parking to wait for <0xae6199f0> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> Feb 10 03:21:45 at
> java.util.concurrent.locks.LockSupport.park(java.base@21.0.1/LockSupport.java:371)
> Feb 10 03:21:45 at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(java.base@21.0.1/AbstractQueuedSynchronizer.java:519)
> Feb 10 03:21:45 at
> java.util.concurrent.ForkJoinPool.unmanagedBlock(java.base@21.0.1/ForkJoinPool.java:3780)
> Feb 10 03:21:45 at
> java.util.concurrent.ForkJoinPool.managedBlock(java.base@21.0.1/ForkJoinPool.java:3725)
> Feb 10 03:21:45 at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@21.0.1/AbstractQueuedSynchronizer.java:1707)
> Feb 10 03:21:45 at
> java.lang.ProcessImpl.waitFor(java.base@21.0.1/ProcessImpl.java:425)
> Feb 10 03:21:45 at
> org.apache.flink.test.recovery.TaskManagerRunnerITCase.testNondeterministicWorkingDirIsDeletedInCaseOfProcessFailure(TaskManagerRunnerITCase.java:126)
> Feb 10 03:21:45 at
> java.lang.invoke.LambdaForm$DMH/0x7fbccb1b8000.invokeVirtual(java.base@21.0.1/LambdaForm$DMH)
> Feb 10 03:21:45 at
> java.lang.invoke.LambdaForm$MH/0x7fbccb1b8800.invoke(java.base@21.0.1/LambdaForm$MH)
> [...]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34404) GroupWindowAggregateProcTimeRestoreTest#testRestore times out
[
https://issues.apache.org/jira/browse/FLINK-34404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34404:
---
Assignee: Alan Sheinberg
> GroupWindowAggregateProcTimeRestoreTest#testRestore times out
> -
>
> Key: FLINK-34404
> URL: https://issues.apache.org/jira/browse/FLINK-34404
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
>Affects Versions: 1.19.0, 1.20.0
>Reporter: Matthias Pohl
>Assignee: Alan Sheinberg
>Priority: Critical
> Labels: test-stability
> Attachments: FLINK-34404.failure.log, FLINK-34404.success.log
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57357=logs=32715a4c-21b8-59a3-4171-744e5ab107eb=ff64056b-5320-5afe-c22c-6fa339e59586=11603
> {code}
> Feb 07 02:17:40 "ForkJoinPool-74-worker-1" #382 daemon prio=5 os_prio=0
> cpu=282.22ms elapsed=961.78s tid=0x7f880a485c00 nid=0x6745 waiting on
> condition [0x7f878a6f9000]
> Feb 07 02:17:40java.lang.Thread.State: WAITING (parking)
> Feb 07 02:17:40 at
> jdk.internal.misc.Unsafe.park(java.base@17.0.7/Native Method)
> Feb 07 02:17:40 - parking to wait for <0xff73d060> (a
> java.util.concurrent.CompletableFuture$Signaller)
> Feb 07 02:17:40 at
> java.util.concurrent.locks.LockSupport.park(java.base@17.0.7/LockSupport.java:211)
> Feb 07 02:17:40 at
> java.util.concurrent.CompletableFuture$Signaller.block(java.base@17.0.7/CompletableFuture.java:1864)
> Feb 07 02:17:40 at
> java.util.concurrent.ForkJoinPool.compensatedBlock(java.base@17.0.7/ForkJoinPool.java:3449)
> Feb 07 02:17:40 at
> java.util.concurrent.ForkJoinPool.managedBlock(java.base@17.0.7/ForkJoinPool.java:3432)
> Feb 07 02:17:40 at
> java.util.concurrent.CompletableFuture.waitingGet(java.base@17.0.7/CompletableFuture.java:1898)
> Feb 07 02:17:40 at
> java.util.concurrent.CompletableFuture.get(java.base@17.0.7/CompletableFuture.java:2072)
> Feb 07 02:17:40 at
> org.apache.flink.table.planner.plan.nodes.exec.testutils.RestoreTestBase.testRestore(RestoreTestBase.java:292)
> Feb 07 02:17:40 at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@17.0.7/Native
> Method)
> Feb 07 02:17:40 at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@17.0.7/NativeMethodAccessorImpl.java:77)
> Feb 07 02:17:40 at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@17.0.7/DelegatingMethodAccessorImpl.java:43)
> Feb 07 02:17:40 at
> java.lang.reflect.Method.invoke(java.base@17.0.7/Method.java:568)
> Feb 07 02:17:40 at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:728)
> [...]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34367) Release Testing Instructions: Verify FLINK-34027 AsyncScalarFunction for asynchronous scalar function support
[ https://issues.apache.org/jira/browse/FLINK-34367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816551#comment-17816551 ] Jing Ge commented on FLINK-34367: - [~twalthr] would you like to take a look at this ticket? > Release Testing Instructions: Verify FLINK-34027 AsyncScalarFunction for > asynchronous scalar function support > - > > Key: FLINK-34367 > URL: https://issues.apache.org/jira/browse/FLINK-34367 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Alan Sheinberg >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34282) Create a release branch
[
https://issues.apache.org/jira/browse/FLINK-34282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816018#comment-17816018
]
Jing Ge commented on FLINK-34282:
-
[~mapohl] please go ahead, thanks!
> Create a release branch
> ---
>
> Key: FLINK-34282
> URL: https://issues.apache.org/jira/browse/FLINK-34282
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.19.0
>Reporter: lincoln lee
>Assignee: lincoln lee
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
> Attachments: screenshot-1.png
>
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
> h4. Flink repository
> Create a branch for the new version that we want to release before updating
> the master branch to the next development version:
> {code:bash}
> $ cd ./tools
> tools $ releasing/create_snapshot_branch.sh
> tools $ git checkout master
> tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION
> NEW_VERSION=$NEXT_SNAPSHOT_VERSION releasing/update_branch_version.sh
> {code}
> In the {{master}} branch, add a new value (e.g. {{v1_16("1.16")}}) to
> [apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
> as the last entry:
> {code:java}
> // ...
> v1_12("1.12"),
> v1_13("1.13"),
> v1_14("1.14"),
> v1_15("1.15"),
> v1_16("1.16");
> {code}
> Additionally in master, update the branch list of the GitHub Actions nightly
> workflow (see
> [apache/flink:.github/workflows/nightly-trigger.yml#L31ff|https://github.com/apache/flink/blob/master/.github/workflows/nightly-trigger.yml#L31]):
> The two most-recent releases and master should be covered.
> The newly created branch and updated {{master}} branch need to be pushed to
> the official repository.
> h4. Flink Docker Repository
> Afterwards fork off from {{dev-master}} a {{dev-x.y}} branch in the
> [apache/flink-docker|https://github.com/apache/flink-docker] repository. Make
> sure that
> [apache/flink-docker:.github/workflows/ci.yml|https://github.com/apache/flink-docker/blob/dev-master/.github/workflows/ci.yml]
> points to the correct snapshot version; for {{dev-x.y}} it should point to
> {{{}x.y-SNAPSHOT{}}}, while for {{dev-master}} it should point to the most
> recent snapshot version (\{[$NEXT_SNAPSHOT_VERSION}}).
> After pushing the new minor release branch, as the last step you should also
> update the documentation workflow to also build the documentation for the new
> release branch. Check [Managing
> Documentation|https://cwiki.apache.org/confluence/display/FLINK/Managing+Documentation]
> on details on how to do that. You may also want to manually trigger a build
> to make the changes visible as soon as possible.
> h4. Flink Benchmark Repository
> First of all, checkout the {{master}} branch to {{dev-x.y}} branch in
> [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks], so that
> we can have a branch named {{dev-x.y}} which could be built on top of
> (${{CURRENT_SNAPSHOT_VERSION}}).
> Then, inside the repository you need to manually update the {{flink.version}}
> property inside the parent *pom.xml* file. It should be pointing to the most
> recent snapshot version ($NEXT_SNAPSHOT_VERSION). For example:
> {code:xml}
> 1.18-SNAPSHOT
> {code}
> h4. AzureCI Project Configuration
> The new release branch needs to be configured within AzureCI to make azure
> aware of the new release branch. This matter can only be handled by Ververica
> employees since they are owning the AzureCI setup.
>
>
> h3. Expectations (Minor Version only if not stated otherwise)
> * Release branch has been created and pushed
> * Changes on the new release branch are picked up by [Azure
> CI|https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary]
> * {{master}} branch has the version information updated to the new version
> (check pom.xml files and
> *
> [apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
> enum)
> *
>
[jira] [Closed] (FLINK-34393) Release Testing Instructions: Verify FLINK-20767 Add nested field support for SupportsFilterPushDown
[ https://issues.apache.org/jira/browse/FLINK-34393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge closed FLINK-34393. --- Resolution: Fixed > Release Testing Instructions: Verify FLINK-20767 Add nested field support for > SupportsFilterPushDown > > > Key: FLINK-34393 > URL: https://issues.apache.org/jira/browse/FLINK-34393 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Venkata krishnan Sowrirajan >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34393) Release Testing Instructions: Verify FLINK-20767 Add nested field support for SupportsFilterPushDown
[ https://issues.apache.org/jira/browse/FLINK-34393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815791#comment-17815791 ] Jing Ge commented on FLINK-34393: - Thanks for the clarification. > Release Testing Instructions: Verify FLINK-20767 Add nested field support for > SupportsFilterPushDown > > > Key: FLINK-34393 > URL: https://issues.apache.org/jira/browse/FLINK-34393 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Venkata krishnan Sowrirajan >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34391) Release Testing Instructions: Verify FLINK-15959 Add min number of slots configuration to limit total number of slots
[ https://issues.apache.org/jira/browse/FLINK-34391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815731#comment-17815731 ] Jing Ge commented on FLINK-34391: - pinged [~xiangyu0xf] in the Slack, waiting for the feedback > Release Testing Instructions: Verify FLINK-15959 Add min number of slots > configuration to limit total number of slots > - > > Key: FLINK-34391 > URL: https://issues.apache.org/jira/browse/FLINK-34391 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: xiangyu feng >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34395) Release Testing Instructions: Verify FLINK-32514 Support using larger checkpointing interval when source is processing backlog
[ https://issues.apache.org/jira/browse/FLINK-34395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815730#comment-17815730 ] Jing Ge commented on FLINK-34395: - pinged [~yunfengzhou] in the Slack, waiting for the feedback > Release Testing Instructions: Verify FLINK-32514 Support using larger > checkpointing interval when source is processing backlog > -- > > Key: FLINK-34395 > URL: https://issues.apache.org/jira/browse/FLINK-34395 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Yunfeng Zhou >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34393) Release Testing Instructions: Verify FLINK-20767 Add nested field support for SupportsFilterPushDown
[ https://issues.apache.org/jira/browse/FLINK-34393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815728#comment-17815728 ] Jing Ge commented on FLINK-34393: - pinged [~vsowrirajan] in the Slack, waiting for the feedback > Release Testing Instructions: Verify FLINK-20767 Add nested field support for > SupportsFilterPushDown > > > Key: FLINK-34393 > URL: https://issues.apache.org/jira/browse/FLINK-34393 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Venkata krishnan Sowrirajan >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34367) Release Testing Instructions: Verify FLINK-34027 AsyncScalarFunction for asynchronous scalar function support
[ https://issues.apache.org/jira/browse/FLINK-34367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815727#comment-17815727 ] Jing Ge commented on FLINK-34367: - Hi [~asheinberg] would you like to create a release testing ticket for your contributed feature? Thanks! > Release Testing Instructions: Verify FLINK-34027 AsyncScalarFunction for > asynchronous scalar function support > - > > Key: FLINK-34367 > URL: https://issues.apache.org/jira/browse/FLINK-34367 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: Alan Sheinberg >Priority: Blocker > Fix For: 1.19.0 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34399) Release Testing: Verify FLINK-33644 Make QueryOperations SQL serializable
[
https://issues.apache.org/jira/browse/FLINK-34399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-34399:
Labels: release-testing (was: )
> Release Testing: Verify FLINK-33644 Make QueryOperations SQL serializable
> -
>
> Key: FLINK-34399
> URL: https://issues.apache.org/jira/browse/FLINK-34399
> Project: Flink
> Issue Type: Sub-task
>Reporter: Dawid Wysakowicz
>Priority: Major
> Labels: release-testing
>
> Test suggestions:
> 1. Write a few Table API programs.
> 2. Call Table.getQueryOperation#asSerializableString, manually verify the
> produced SQL query
> 3. Check the produced SQL query is runnable and produces the same results as
> the Table API program:
> {code}
> Table table = tEnv.from("a") ...
> String sqlQuery = table.getQueryOperation().asSerializableString();
> //verify the sqlQuery is runnable
> tEnv.sqlQuery(sqlQuery).execute().collect()
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34305) Release Testing Instructions: Verify FLINK-33261 Support Setting Parallelism for Table/SQL Sources
[ https://issues.apache.org/jira/browse/FLINK-34305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815724#comment-17815724 ] Jing Ge commented on FLINK-34305: - Hi [~sudewei.sdw] I have assigned this ticket to you > Release Testing Instructions: Verify FLINK-33261 Support Setting Parallelism > for Table/SQL Sources > --- > > Key: FLINK-34305 > URL: https://issues.apache.org/jira/browse/FLINK-34305 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: SuDewei >Priority: Blocker > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-34305) Release Testing Instructions: Verify FLINK-33261 Support Setting Parallelism for Table/SQL Sources
[ https://issues.apache.org/jira/browse/FLINK-34305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34305: --- Assignee: SuDewei (was: Zhanghao Chen) > Release Testing Instructions: Verify FLINK-33261 Support Setting Parallelism > for Table/SQL Sources > --- > > Key: FLINK-34305 > URL: https://issues.apache.org/jira/browse/FLINK-34305 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API >Affects Versions: 1.19.0 >Reporter: lincoln lee >Assignee: SuDewei >Priority: Blocker > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FLINK-33843) Promote release 1.18.1
[
https://issues.apache.org/jira/browse/FLINK-33843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33843.
-
Resolution: Fixed
> Promote release 1.18.1
> --
>
> Key: FLINK-33843
> URL: https://issues.apache.org/jira/browse/FLINK-33843
> Project: Flink
> Issue Type: New Feature
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> Once the release has been finalized, the last step of the process is to
> promote the release within the project and beyond. Please wait for 24h after
> finalizing the release in accordance with the [ASF release
> policy|http://www.apache.org/legal/release-policy.html#release-announcements].
> *Final checklist to declare this issue resolved:*
> # Website pull request to [list the
> release|http://flink.apache.org/downloads.html] merged
> # Release announced on the user@ mailing list.
> # Blog post published, if applicable.
> # Release recorded in
> [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink].
> # Release announced on social media.
> # Completion declared on the dev@ mailing list.
> # Update Homebrew:
> [https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request] (seems to be done
> automatically - at least for minor releases for both minor and major
> releases)
> # Updated the japicmp configuration
> ** corresponding SNAPSHOT branch japicmp reference version set to the just
> released version, and API compatibiltity checks for {{@PublicEvolving}} was
> enabled
> ** (minor version release only) master branch japicmp reference version set
> to the just released version
> ** (minor version release only) master branch japicmp exclusions have been
> cleared
> # Update the list of previous version in {{docs/config.toml}} on the master
> branch.
> # Set {{show_outdated_warning: true}} in {{docs/config.toml}} in the branch
> of the _now deprecated_ Flink version (i.e. 1.16 if 1.18.0 is released)
> # Update stable and master alias in
> [https://github.com/apache/flink/blob/master/.github/workflows/docs.yml]
> # Open discussion thread for End of Life for Unsupported version (i.e. 1.16)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-33838) Finalize release 1.18.1
[ https://issues.apache.org/jira/browse/FLINK-33838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge resolved FLINK-33838. - Resolution: Fixed > Finalize release 1.18.1 > --- > > Key: FLINK-33838 > URL: https://issues.apache.org/jira/browse/FLINK-33838 > Project: Flink > Issue Type: New Feature >Affects Versions: 1.18.0 >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > Once the release candidate has been reviewed and approved by the community, > the release should be finalized. This involves the final deployment of the > release candidate to the release repositories, merging of the website > changes, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FLINK-33842) Publish the Dockerfiles for the new release
[
https://issues.apache.org/jira/browse/FLINK-33842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33842.
-
Resolution: Fixed
> Publish the Dockerfiles for the new release
> ---
>
> Key: FLINK-33842
> URL: https://issues.apache.org/jira/browse/FLINK-33842
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> Note: the official Dockerfiles fetch the binary distribution of the target
> Flink version from an Apache mirror. After publishing the binary release
> artifacts, mirrors can take some hours to start serving the new artifacts, so
> you may want to wait to do this step until you are ready to continue with the
> "Promote the release" steps in the follow-up Jira.
> Follow the [release instructions in the flink-docker
> repo|https://github.com/apache/flink-docker#release-workflow] to build the
> new Dockerfiles and send an updated manifest to Docker Hub so the new images
> are built and published.
> Note: the flink-web PR has to be merged before the pull request to be opened
> on the
> [{{official-images}}|https://github.com/docker-library/official-images] repo.
>
> h3. Expectations
> * Dockerfiles in [flink-docker|https://github.com/apache/flink-docker]
> updated for the new Flink release and pull request opened on the Docker
> official-images with an updated manifest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33588) Fix Flink Checkpointing Statistics Bug
[ https://issues.apache.org/jira/browse/FLINK-33588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798545#comment-17798545 ] Jing Ge edited comment on FLINK-33588 at 1/25/24 11:03 PM: --- [~zhutong66] Thanks for the feedback. Could you please elaborate on how you will create the test? The test should be part of the CI and used as regression tests. was (Author: jingge): [~zhutong66] Thanks for the feedback. Could you please elaborate on what you will create the test? The test should be part of the CI and used as regression tests. > Fix Flink Checkpointing Statistics Bug > -- > > Key: FLINK-33588 > URL: https://issues.apache.org/jira/browse/FLINK-33588 > Project: Flink > Issue Type: Bug > Components: Runtime / Checkpointing >Affects Versions: 1.14.5, 1.16.0, 1.17.0, 1.15.2, 1.14.6, 1.18.0, 1.17.1 >Reporter: Tongtong Zhu >Assignee: Tongtong Zhu >Priority: Critical > Labels: pull-request-available > Fix For: 1.19.0, 1.18.1 > > Attachments: FLINK-33588.patch, image-2023-12-11-17-35-23-391.png, > image-2023-12-13-11-35-43-780.png, image-2023-12-15-13-59-28-201.png, > image-2023-12-19-14-02-49-083.png, image-2023-12-19-14-03-27-062.png, > newCommit-FLINK-33688.patch > > > When the Flink task is first started, the checkpoint data is null due to the > lack of data, and Percentile throws a null pointer exception when calculating > the percentage. After multiple tests, I found that it is necessary to set an > initial value for the statistical data value of the checkpoint when the > checkpoint data is null (i.e. at the beginning of the task) to solve this > problem. > The following is an abnormal description of the bug： > 2023-09-13 15:02:54,608 ERROR > org.apache.flink.runtime.rest.handler.job.checkpoints.CheckpointingStatisticsHandler > [] - Unhandled exception. > org.apache.commons.math3.exception.NullArgumentException: input array > at > org.apache.commons.math3.util.MathArrays.verifyValues(MathArrays.java:1650) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.commons.math3.stat.descriptive.AbstractUnivariateStatistic.test(AbstractUnivariateStatistic.java:158) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.commons.math3.stat.descriptive.rank.Percentile.evaluate(Percentile.java:272) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.commons.math3.stat.descriptive.rank.Percentile.evaluate(Percentile.java:241) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.metrics.DescriptiveStatisticsHistogramStatistics$CommonMetricsSnapshot.getPercentile(DescriptiveStatisticsHistogramStatistics.java:159) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.metrics.DescriptiveStatisticsHistogramStatistics.getQuantile(DescriptiveStatisticsHistogramStatistics.java:53) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.checkpoint.StatsSummarySnapshot.getQuantile(StatsSummarySnapshot.java:108) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.rest.messages.checkpoints.StatsSummaryDto.valueOf(StatsSummaryDto.java:81) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.rest.handler.job.checkpoints.CheckpointingStatisticsHandler.createCheckpointingStatistics(CheckpointingStatisticsHandler.java:129) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.rest.handler.job.checkpoints.CheckpointingStatisticsHandler.handleRequest(CheckpointingStatisticsHandler.java:84) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.rest.handler.job.checkpoints.CheckpointingStatisticsHandler.handleRequest(CheckpointingStatisticsHandler.java:58) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.rest.handler.job.AbstractAccessExecutionGraphHandler.handleRequest(AbstractAccessExecutionGraphHandler.java:68) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > org.apache.flink.runtime.rest.handler.job.AbstractExecutionGraphHandler.lambda$handleRequest$0(AbstractExecutionGraphHandler.java:87) > ~[flink-dist_2.12-1.14.5.jar:1.14.5] > at > java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > [?:1.8.0_151] > at > java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > [?:1.8.0_151] > at > java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442) > [?:1.8.0_151] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [?:1.8.0_151] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_151] > at >
[jira] [Assigned] (FLINK-34236) Evaluate strange unstable build after cleaning up CI machines
[ https://issues.apache.org/jira/browse/FLINK-34236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34236: --- Assignee: Jeyhun Karimov > Evaluate strange unstable build after cleaning up CI machines > - > > Key: FLINK-34236 > URL: https://issues.apache.org/jira/browse/FLINK-34236 > Project: Flink > Issue Type: Improvement > Components: Test Infrastructure >Reporter: Jing Ge >Assignee: Jeyhun Karimov >Priority: Minor > > To check if it is one time issue because infra change or not. > > https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56601=logs=e9d3d34f-3d15-59f4-0e3e-35067d100dfe=5d91035e-8022-55f2-2d4f-ab121508bf7e -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34236) Evaluate strange unstable build after cleaning up CI machines
Jing Ge created FLINK-34236: --- Summary: Evaluate strange unstable build after cleaning up CI machines Key: FLINK-34236 URL: https://issues.apache.org/jira/browse/FLINK-34236 Project: Flink Issue Type: Improvement Components: Test Infrastructure Reporter: Jing Ge To check if it is one time issue because infra change or not. https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56601=logs=e9d3d34f-3d15-59f4-0e3e-35067d100dfe=5d91035e-8022-55f2-2d4f-ab121508bf7e -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33842) Publish the Dockerfiles for the new release
[
https://issues.apache.org/jira/browse/FLINK-33842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809850#comment-17809850
]
Jing Ge commented on FLINK-33842:
-
official-image PR: https://github.com/docker-library/official-images/pull/16114
> Publish the Dockerfiles for the new release
> ---
>
> Key: FLINK-33842
> URL: https://issues.apache.org/jira/browse/FLINK-33842
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> Note: the official Dockerfiles fetch the binary distribution of the target
> Flink version from an Apache mirror. After publishing the binary release
> artifacts, mirrors can take some hours to start serving the new artifacts, so
> you may want to wait to do this step until you are ready to continue with the
> "Promote the release" steps in the follow-up Jira.
> Follow the [release instructions in the flink-docker
> repo|https://github.com/apache/flink-docker#release-workflow] to build the
> new Dockerfiles and send an updated manifest to Docker Hub so the new images
> are built and published.
> Note: the flink-web PR has to be merged before the pull request to be opened
> on the
> [{{official-images}}|https://github.com/docker-library/official-images] repo.
>
> h3. Expectations
> * Dockerfiles in [flink-docker|https://github.com/apache/flink-docker]
> updated for the new Flink release and pull request opened on the Docker
> official-images with an updated manifest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-34165) It seems that Apache download link has been changed
[ https://issues.apache.org/jira/browse/FLINK-34165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge resolved FLINK-34165. - Resolution: Fixed > It seems that Apache download link has been changed > --- > > Key: FLINK-34165 > URL: https://issues.apache.org/jira/browse/FLINK-34165 > Project: Flink > Issue Type: Bug > Components: flink-docker >Affects Versions: 1.15.4, 1.16.3, 1.17.2, 1.18.1 >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > Labels: pull-request-available > Attachments: image-2024-01-19-07-55-07-775.png > > > For example, the link > [https://www.apache.org/dist/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc][1] > worked previously now redirect to a list page which leads to a wrong > flink.tgz.asc with HTML instead of expected signature. > !image-2024-01-19-07-55-07-775.png! > The link should be replace with > [https://downloads.apache.org/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc] > > [1] > [https://github.com/apache/flink-docker/blob/627987997ca7ec86bcc3d80b26df58aa595b91af/1.17/scala_2.12-java11-ubuntu/Dockerfile#L48C19-L48C101] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FLINK-33824) Prepare Flink 1.18.1 Release
[
https://issues.apache.org/jira/browse/FLINK-33824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33824.
-
Resolution: Fixed
> Prepare Flink 1.18.1 Release
>
>
> Key: FLINK-33824
> URL: https://issues.apache.org/jira/browse/FLINK-33824
> Project: Flink
> Issue Type: New Feature
> Components: Release System
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> This umbrella issue is meant as a test balloon for moving the [release
> documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
> into Jira.
> h3. Prerequisites
> h4. Environment Variables
> Commands in the subtasks might expect some of the following enviroment
> variables to be set accordingly to the version that is about to be released:
> {code:bash}
> RELEASE_VERSION="1.18.1"
> SHORT_RELEASE_VERSION="1.18"
> CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
> {code}
> h4. Build Tools
> All of the following steps require to use Maven 3.2.5 and Java 8. Modify your
> PATH environment variable accordingly if needed.
> h4. Flink Source
> * Create a new directory for this release and clone the Flink repository
> from Github to ensure you have a clean workspace (this step is optional).
> * Run {{mvn -Prelease clean install}} to ensure that the build processes
> that are specific to that profile are in good shape (this step is optional).
> The rest of this instructions assumes that commands are run in the root (or
> {{./tools}} directory) of a repository on the branch of the release version
> with the above environment variables set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33846) Remove outdated versions (need PMC role)
[
https://issues.apache.org/jira/browse/FLINK-33846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33846:
Description:
h4. dist.apache.org
For a new bugfix version remove all release files for previous bugfix releases
in the same series, e.g., when releasing 1.18.1, remove the 1.18.0 release.
# If you have not already, check out the Flink section of the {{release}}
repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion. In
a fresh directory:
{code:java}
svn checkout https://dist.apache.org/repos/dist/release/flink --depth=immediates
cd flink
{code}
# Remove files for outdated releases and commit the changes.
{code:java}
svn remove flink-
svn commit
{code}
# Verify that files are
[removed|https://dist.apache.org/repos/dist/release/flink]
(!) Remember to remove the corresponding download links from the website.
h4. CI
Disable the cron job for the now-unsupported version from
(tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
in the respective branch.
was:
h4. dist.apache.org
For a new bugfix version remove all release files for previous bugfix releases
in the same series, e.g., when releasing 1.7.1, remove the 1.7.0 release.
# If you have not already, check out the Flink section of the {{release}}
repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion. In
a fresh directory:
{code:java}
svn checkout https://dist.apache.org/repos/dist/release/flink --depth=immediates
cd flink
{code}
# Remove files for outdated releases and commit the changes.
{code:java}
svn remove flink-
svn commit
{code}
# Verify that files are
[removed|https://dist.apache.org/repos/dist/release/flink]
(!) Remember to remove the corresponding download links from the website.
h4. CI
Disable the cron job for the now-unsupported version from
(tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
in the respective branch.
> Remove outdated versions (need PMC role)
>
>
> Key: FLINK-33846
> URL: https://issues.apache.org/jira/browse/FLINK-33846
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Priority: Major
>
> h4. dist.apache.org
> For a new bugfix version remove all release files for previous bugfix
> releases in the same series, e.g., when releasing 1.18.1, remove the 1.18.0
> release.
> # If you have not already, check out the Flink section of the {{release}}
> repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion.
> In a fresh directory:
> {code:java}
> svn checkout https://dist.apache.org/repos/dist/release/flink
> --depth=immediates
> cd flink
> {code}
> # Remove files for outdated releases and commit the changes.
> {code:java}
> svn remove flink-
> svn commit
> {code}
> # Verify that files are
> [removed|https://dist.apache.org/repos/dist/release/flink]
> (!) Remember to remove the corresponding download links from the website.
> h4. CI
> Disable the cron job for the now-unsupported version from
> (tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
> in the respective branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-33850) Updates the docs stable version
[
https://issues.apache.org/jira/browse/FLINK-33850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33850.
-
Resolution: Fixed
> Updates the docs stable version
> ---
>
> Key: FLINK-33850
> URL: https://issues.apache.org/jira/browse/FLINK-33850
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> Update docs to "stable" in {{docs/config.toml}} in the branch of the
> _just-released_ version:
> * Change V{{{}ersion{}}} from {{{}x.y.z }}to \{{{}x.y.z{}}}, i.e. {{1.18.0}}
> to {{1.18.1}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-33848) Other announcements
[ https://issues.apache.org/jira/browse/FLINK-33848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge resolved FLINK-33848. - Resolution: Fixed > Other announcements > --- > > Key: FLINK-33848 > URL: https://issues.apache.org/jira/browse/FLINK-33848 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > h3. Recordkeeping > Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] > to seed the information about the release into future project reports. > (Note: Only PMC members have access report releases. If you do not have > access, ask on the mailing list for assistance.) > h3. Flink blog > Example: > [https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/] > > h3. Social media > Tweet, post on Facebook, LinkedIn, and other platforms. Ask other > contributors to do the same. > h3. Flink Release Wiki page > Add a summary of things that went well or that went not so well during the > release process. This can include feedback from contributors but also more > generic things like the release have taken longer than initially anticipated > (and why) to give a bit of context to the release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FLINK-33844) Update japicmp configuration
[
https://issues.apache.org/jira/browse/FLINK-33844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33844.
-
Resolution: Fixed
> Update japicmp configuration
>
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.2
>
>
> Update the japicmp reference version and wipe exclusions / enable API
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see
> below).
> For a new major release (x.y.0), run the same command also on the master
> branch for updating the japicmp reference version and removing out-dated
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central.
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for
> $RELEASE_VERSION" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-33847) Apache mailing lists announcements
[
https://issues.apache.org/jira/browse/FLINK-33847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33847.
-
Resolution: Fixed
> Apache mailing lists announcements
> --
>
> Key: FLINK-33847
> URL: https://issues.apache.org/jira/browse/FLINK-33847
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> Announce on the {{dev@}} mailing list that the release has been finished.
> Announce on the release on the {{user@}} mailing list, listing major
> improvements and contributions.
> Announce the release on the [annou...@apache.org|mailto:annou...@apache.org]
> mailing list.
> {panel}
> {panel}
> |{{From: Release Manager}}
> {{To: d...@flink.apache.org, u...@flink.apache.org, user...@flink.apache.org,
> annou...@apache.org}}
> {{Subject: [ANNOUNCE] Apache Flink 1.2.3 released}}
>
> {{The Apache Flink community is very happy to announce the release of Apache
> Flink 1.2.3, which is the third bugfix release for the Apache Flink 1.2
> series.}}
>
> {{Apache Flink® is an open-source stream processing framework for
> distributed, high-performing, always-available, and accurate data streaming
> applications.}}
>
> {{The release is available for download at:}}
> {{[https://flink.apache.org/downloads.html]}}
>
> {{Please check out the release blog post for an overview of the improvements
> for this bugfix release:}}
> {{}}
>
> {{The full release notes are available in Jira:}}
> {{}}
>
> {{We would like to thank all contributors of the Apache Flink community who
> made this release possible!}}
>
> {{Feel free to reach out to the release managers (or respond to this thread)
> with feedback on the release process. Our goal is to constantly improve the
> release process. Feedback on what could be improved or things that didn't go
> so well are appreciated.}}
>
> {{Regards,}}
> {{Release Manager}}|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-33847) Apache mailing lists announcements
[
https://issues.apache.org/jira/browse/FLINK-33847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808730#comment-17808730
]
Jing Ge commented on FLINK-33847:
-
https://lists.apache.org/thread/p5f4j11nylvhw15knvlbzjzynh13t65w
> Apache mailing lists announcements
> --
>
> Key: FLINK-33847
> URL: https://issues.apache.org/jira/browse/FLINK-33847
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> Announce on the {{dev@}} mailing list that the release has been finished.
> Announce on the release on the {{user@}} mailing list, listing major
> improvements and contributions.
> Announce the release on the [annou...@apache.org|mailto:annou...@apache.org]
> mailing list.
> {panel}
> {panel}
> |{{From: Release Manager}}
> {{To: d...@flink.apache.org, u...@flink.apache.org, user...@flink.apache.org,
> annou...@apache.org}}
> {{Subject: [ANNOUNCE] Apache Flink 1.2.3 released}}
>
> {{The Apache Flink community is very happy to announce the release of Apache
> Flink 1.2.3, which is the third bugfix release for the Apache Flink 1.2
> series.}}
>
> {{Apache Flink® is an open-source stream processing framework for
> distributed, high-performing, always-available, and accurate data streaming
> applications.}}
>
> {{The release is available for download at:}}
> {{[https://flink.apache.org/downloads.html]}}
>
> {{Please check out the release blog post for an overview of the improvements
> for this bugfix release:}}
> {{}}
>
> {{The full release notes are available in Jira:}}
> {{}}
>
> {{We would like to thank all contributors of the Apache Flink community who
> made this release possible!}}
>
> {{Feel free to reach out to the release managers (or respond to this thread)
> with feedback on the release process. Our goal is to constantly improve the
> release process. Feedback on what could be improved or things that didn't go
> so well are appreciated.}}
>
> {{Regards,}}
> {{Release Manager}}|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-33845) Merge website pull request
[ https://issues.apache.org/jira/browse/FLINK-33845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge resolved FLINK-33845. - Resolution: Fixed > Merge website pull request > -- > > Key: FLINK-33845 > URL: https://issues.apache.org/jira/browse/FLINK-33845 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > Labels: pull-request-available > > Merge the website pull request to [list the > release|http://flink.apache.org/downloads.html]. > Make sure to regenerate the website as well, as it isn't build automatically: > # install Hugo on the local machine > # build the website > # create a PR -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FLINK-33885) Build Release Candidate: 1.18.1-rc2
[
https://issues.apache.org/jira/browse/FLINK-33885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33885.
-
Resolution: Fixed
> Build Release Candidate: 1.18.1-rc2
> ---
>
> Key: FLINK-33885
> URL: https://issues.apache.org/jira/browse/FLINK-33885
> Project: Flink
> Issue Type: New Feature
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> The core of the release process is the build-vote-fix cycle. Each cycle
> produces one release candidate. The Release Manager repeats this cycle until
> the community approves one release candidate, which is then finalized.
> h4. Prerequisites
> Set up a few environment variables to simplify Maven commands that follow.
> This identifies the release candidate being built. Start with {{RC_NUM}}
> equal to 1 and increment it for each candidate:
> {code}
> RC_NUM="1"
> TAG="release-${RELEASE_VERSION}-rc${RC_NUM}"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FLINK-33888) Propose a pull request for website updates
[
https://issues.apache.org/jira/browse/FLINK-33888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge resolved FLINK-33888.
-
Resolution: Fixed
> Propose a pull request for website updates
> --
>
> Key: FLINK-33888
> URL: https://issues.apache.org/jira/browse/FLINK-33888
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> The final step of building the candidate is to propose a website pull request
> containing the following changes:
> * update docs/data/flink.yml
> *
> ** Add a new major version or update minor version as required
> * update docs/data/release_archive.yml
> * add a blog post announcing the release in {{docs/content/posts}}
> (!) Don’t merge the PRs before finalizing the release.
>
>
> h3. Expectations
> * Website pull request proposed to list the
> [release|http://flink.apache.org/downloads.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33846) Remove outdated versions (need PMC role)
[
https://issues.apache.org/jira/browse/FLINK-33846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33846:
Description:
h4. dist.apache.org
For a new bugfix version remove all release files for previous bugfix releases
in the same series, e.g., when releasing 1.7.1, remove the 1.7.0 release.
# If you have not already, check out the Flink section of the {{release}}
repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion. In
a fresh directory:
{code:java}
svn checkout https://dist.apache.org/repos/dist/release/flink --depth=immediates
cd flink
{code}
# Remove files for outdated releases and commit the changes.
{code:java}
svn remove flink-
svn commit
{code}
# Verify that files are
[removed|https://dist.apache.org/repos/dist/release/flink]
(!) Remember to remove the corresponding download links from the website.
h4. CI
Disable the cron job for the now-unsupported version from
(tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
in the respective branch.
was:
h4. dist.apache.org
For a new major release remove all release files older than 2 versions, e.g.,
when releasing 1.7, remove all releases <= 1.5.
For a new bugfix version remove all release files for previous bugfix releases
in the same series, e.g., when releasing 1.7.1, remove the 1.7.0 release.
# If you have not already, check out the Flink section of the {{release}}
repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion. In
a fresh directory:
{code}
svn checkout https://dist.apache.org/repos/dist/release/flink --depth=immediates
cd flink
{code}
# Remove files for outdated releases and commit the changes.
{code}
svn remove flink-
svn commit
{code}
# Verify that files are
[removed|https://dist.apache.org/repos/dist/release/flink]
(!) Remember to remove the corresponding download links from the website.
h4. CI
Disable the cron job for the now-unsupported version from
(tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
in the respective branch.
> Remove outdated versions (need PMC role)
>
>
> Key: FLINK-33846
> URL: https://issues.apache.org/jira/browse/FLINK-33846
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Priority: Major
>
> h4. dist.apache.org
> For a new bugfix version remove all release files for previous bugfix
> releases in the same series, e.g., when releasing 1.7.1, remove the 1.7.0
> release.
> # If you have not already, check out the Flink section of the {{release}}
> repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion.
> In a fresh directory:
> {code:java}
> svn checkout https://dist.apache.org/repos/dist/release/flink
> --depth=immediates
> cd flink
> {code}
> # Remove files for outdated releases and commit the changes.
> {code:java}
> svn remove flink-
> svn commit
> {code}
> # Verify that files are
> [removed|https://dist.apache.org/repos/dist/release/flink]
> (!) Remember to remove the corresponding download links from the website.
> h4. CI
> Disable the cron job for the now-unsupported version from
> (tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
> in the respective branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34135) A number of ci failures with Access to the path '.../_work/_temp/containerHandlerInvoker.js' is denied.
[
https://issues.apache.org/jira/browse/FLINK-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808623#comment-17808623
]
Jing Ge commented on FLINK-34135:
-
gotcha, thanks! Let's keep this ticket open for a few more days.
> A number of ci failures with Access to the path
> '.../_work/_temp/containerHandlerInvoker.js' is denied.
> ---
>
> Key: FLINK-34135
> URL: https://issues.apache.org/jira/browse/FLINK-34135
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
>Reporter: Sergey Nuyanzin
>Assignee: Jeyhun Karimov
>Priority: Blocker
> Labels: test-stability
>
> There is a number of builds failing with something like
> {noformat}
> ##[error]Access to the path
> '/home/agent03/myagent/_work/_temp/containerHandlerInvoker.js' is denied.
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56490=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=fb588352-ef18-568d-b447-699986250ccb
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=554d7c3f-d38e-55f4-96b4-ada3a9cb7d6f=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=fa307d6d-91b1-5ab6-d460-ef50f552b1fe=1798d435-832b-51fe-a9ad-efb9abf4ab04=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=a1ac4ce4-9a4f-5fdb-3290-7e163fba19dc=e4c57254-ec06-5788-3f8e-5ad5dffb418e=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=2c3cbe13-dee0-5837-cf47-3053da9a8a78=56881383-f398-5091-6b3b-22a7eeb7cfa8=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=b0a398c0-685b-599c-eb57-c8c2a771138e=2d9c27d0-8dbb-5be9-7271-453f74f48ab3=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=162f98f7-8967-5f47-2782-a1e178ec2ad3=c9934c56-710d-5f85-d2b8-28ec1fd700ed=9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33845) Merge website pull request
[ https://issues.apache.org/jira/browse/FLINK-33845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-33845: Description: Merge the website pull request to [list the release|http://flink.apache.org/downloads.html]. Make sure to regenerate the website as well, as it isn't build automatically: # install Hugo on the local machine # build the website # create a PR was:Merge the website pull request to [list the release|http://flink.apache.org/downloads.html]. Make sure to regenerate the website as well, as it isn't build automatically. > Merge website pull request > -- > > Key: FLINK-33845 > URL: https://issues.apache.org/jira/browse/FLINK-33845 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > Labels: pull-request-available > > Merge the website pull request to [list the > release|http://flink.apache.org/downloads.html]. > Make sure to regenerate the website as well, as it isn't build automatically: > # install Hugo on the local machine > # build the website > # create a PR -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34135) A number of ci failures with Access to the path '.../_work/_temp/containerHandlerInvoker.js' is denied.
[
https://issues.apache.org/jira/browse/FLINK-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808606#comment-17808606
]
Jing Ge commented on FLINK-34135:
-
[~Sergey Nuyanzin] thanks for letting us know. After checking the example
build, it was e2e test failures which should have less to do with the CI
machines. WDYT?
> A number of ci failures with Access to the path
> '.../_work/_temp/containerHandlerInvoker.js' is denied.
> ---
>
> Key: FLINK-34135
> URL: https://issues.apache.org/jira/browse/FLINK-34135
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
>Reporter: Sergey Nuyanzin
>Assignee: Jeyhun Karimov
>Priority: Blocker
> Labels: test-stability
>
> There is a number of builds failing with something like
> {noformat}
> ##[error]Access to the path
> '/home/agent03/myagent/_work/_temp/containerHandlerInvoker.js' is denied.
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56490=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=fb588352-ef18-568d-b447-699986250ccb
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=554d7c3f-d38e-55f4-96b4-ada3a9cb7d6f=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=fa307d6d-91b1-5ab6-d460-ef50f552b1fe=1798d435-832b-51fe-a9ad-efb9abf4ab04=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=a1ac4ce4-9a4f-5fdb-3290-7e163fba19dc=e4c57254-ec06-5788-3f8e-5ad5dffb418e=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=2c3cbe13-dee0-5837-cf47-3053da9a8a78=56881383-f398-5091-6b3b-22a7eeb7cfa8=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=b0a398c0-685b-599c-eb57-c8c2a771138e=2d9c27d0-8dbb-5be9-7271-453f74f48ab3=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=162f98f7-8967-5f47-2782-a1e178ec2ad3=c9934c56-710d-5f85-d2b8-28ec1fd700ed=9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34165) It seems that Apache download link has been changed
[ https://issues.apache.org/jira/browse/FLINK-34165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34165: --- Assignee: Jing Ge > It seems that Apache download link has been changed > --- > > Key: FLINK-34165 > URL: https://issues.apache.org/jira/browse/FLINK-34165 > Project: Flink > Issue Type: Bug > Components: flink-docker >Affects Versions: 1.15.4, 1.16.3, 1.17.2, 1.18.1 >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > Attachments: image-2024-01-19-07-55-07-775.png > > > For example, the link > [https://www.apache.org/dist/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc][1] > worked previously now redirect to a list page which leads to a wrong > flink.tgz.asc with HTML instead of expected signature. > !image-2024-01-19-07-55-07-775.png! > The link should be replace with > [https://downloads.apache.org/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc] > > [1] > [https://github.com/apache/flink-docker/blob/627987997ca7ec86bcc3d80b26df58aa595b91af/1.17/scala_2.12-java11-ubuntu/Dockerfile#L48C19-L48C101] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34165) It seems that Apache download link has been changed
[ https://issues.apache.org/jira/browse/FLINK-34165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-34165: Description: For example, the link [https://www.apache.org/dist/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc][1] worked previously now redirect to a list page which leads to a wrong flink.tgz.asc with HTML instead of expected signature. !image-2024-01-19-07-55-07-775.png! The link should be replace with [https://downloads.apache.org/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc] [1] [https://github.com/apache/flink-docker/blob/627987997ca7ec86bcc3d80b26df58aa595b91af/1.17/scala_2.12-java11-ubuntu/Dockerfile#L48C19-L48C101] was: The link [https://www.apache.org/dist/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc][1] worked previously now redirect to a list page which leads to a wrong flink.tgz.asc with HTML instead of expected signature. !image-2024-01-19-07-55-07-775.png! The link should be replace with https://downloads.apache.org/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc [1] https://github.com/apache/flink-docker/blob/627987997ca7ec86bcc3d80b26df58aa595b91af/1.17/scala_2.12-java11-ubuntu/Dockerfile#L48C19-L48C101 > It seems that Apache download link has been changed > --- > > Key: FLINK-34165 > URL: https://issues.apache.org/jira/browse/FLINK-34165 > Project: Flink > Issue Type: Bug > Components: flink-docker >Affects Versions: 1.15.4, 1.16.3, 1.17.2, 1.18.1 >Reporter: Jing Ge >Priority: Major > Attachments: image-2024-01-19-07-55-07-775.png > > > For example, the link > [https://www.apache.org/dist/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc][1] > worked previously now redirect to a list page which leads to a wrong > flink.tgz.asc with HTML instead of expected signature. > !image-2024-01-19-07-55-07-775.png! > The link should be replace with > [https://downloads.apache.org/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc] > > [1] > [https://github.com/apache/flink-docker/blob/627987997ca7ec86bcc3d80b26df58aa595b91af/1.17/scala_2.12-java11-ubuntu/Dockerfile#L48C19-L48C101] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34165) It seems that Apache download link has been changed
Jing Ge created FLINK-34165: --- Summary: It seems that Apache download link has been changed Key: FLINK-34165 URL: https://issues.apache.org/jira/browse/FLINK-34165 Project: Flink Issue Type: Bug Components: flink-docker Affects Versions: 1.18.1, 1.17.2, 1.16.3, 1.15.4 Reporter: Jing Ge Attachments: image-2024-01-19-07-55-07-775.png The link [https://www.apache.org/dist/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc][1] worked previously now redirect to a list page which leads to a wrong flink.tgz.asc with HTML instead of expected signature. !image-2024-01-19-07-55-07-775.png! The link should be replace with https://downloads.apache.org/flink/flink-1.17.2/flink-1.17.2-bin-scala_2.12.tgz.asc [1] https://github.com/apache/flink-docker/blob/627987997ca7ec86bcc3d80b26df58aa595b91af/1.17/scala_2.12-java11-ubuntu/Dockerfile#L48C19-L48C101 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34135) A number of ci failures with Access to the path '.../_work/_temp/containerHandlerInvoker.js' is denied.
[
https://issues.apache.org/jira/browse/FLINK-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808492#comment-17808492
]
Jing Ge commented on FLINK-34135:
-
CI works again, I will close this ticket. [~mapohl] [~Sergey Nuyanzin] could
you please double confirm?
> A number of ci failures with Access to the path
> '.../_work/_temp/containerHandlerInvoker.js' is denied.
> ---
>
> Key: FLINK-34135
> URL: https://issues.apache.org/jira/browse/FLINK-34135
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
>Reporter: Sergey Nuyanzin
>Assignee: Jeyhun Karimov
>Priority: Blocker
> Labels: test-stability
>
> There is a number of builds failing with something like
> {noformat}
> ##[error]Access to the path
> '/home/agent03/myagent/_work/_temp/containerHandlerInvoker.js' is denied.
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56490=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=fb588352-ef18-568d-b447-699986250ccb
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=554d7c3f-d38e-55f4-96b4-ada3a9cb7d6f=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=fa307d6d-91b1-5ab6-d460-ef50f552b1fe=1798d435-832b-51fe-a9ad-efb9abf4ab04=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=a1ac4ce4-9a4f-5fdb-3290-7e163fba19dc=e4c57254-ec06-5788-3f8e-5ad5dffb418e=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=2c3cbe13-dee0-5837-cf47-3053da9a8a78=56881383-f398-5091-6b3b-22a7eeb7cfa8=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=b0a398c0-685b-599c-eb57-c8c2a771138e=2d9c27d0-8dbb-5be9-7271-453f74f48ab3=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=162f98f7-8967-5f47-2782-a1e178ec2ad3=c9934c56-710d-5f85-d2b8-28ec1fd700ed=9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34135) A number of ci failures with Access to the path '.../_work/_temp/containerHandlerInvoker.js' is denied.
[
https://issues.apache.org/jira/browse/FLINK-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807802#comment-17807802
]
Jing Ge commented on FLINK-34135:
-
[~Sergey Nuyanzin] it looks like most failed builds were running on
AlibabaCI001, correct?
> A number of ci failures with Access to the path
> '.../_work/_temp/containerHandlerInvoker.js' is denied.
> ---
>
> Key: FLINK-34135
> URL: https://issues.apache.org/jira/browse/FLINK-34135
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
>Reporter: Sergey Nuyanzin
>Assignee: Jeyhun Karimov
>Priority: Blocker
> Labels: test-stability
>
> There is a number of builds failing with something like
> {noformat}
> ##[error]Access to the path
> '/home/agent03/myagent/_work/_temp/containerHandlerInvoker.js' is denied.
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56490=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=fb588352-ef18-568d-b447-699986250ccb
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=554d7c3f-d38e-55f4-96b4-ada3a9cb7d6f=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=fa307d6d-91b1-5ab6-d460-ef50f552b1fe=1798d435-832b-51fe-a9ad-efb9abf4ab04=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=a1ac4ce4-9a4f-5fdb-3290-7e163fba19dc=e4c57254-ec06-5788-3f8e-5ad5dffb418e=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=2c3cbe13-dee0-5837-cf47-3053da9a8a78=56881383-f398-5091-6b3b-22a7eeb7cfa8=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=b0a398c0-685b-599c-eb57-c8c2a771138e=2d9c27d0-8dbb-5be9-7271-453f74f48ab3=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=162f98f7-8967-5f47-2782-a1e178ec2ad3=c9934c56-710d-5f85-d2b8-28ec1fd700ed=9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34135) A number of ci failures with Access to the path '.../_work/_temp/containerHandlerInvoker.js' is denied.
[
https://issues.apache.org/jira/browse/FLINK-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807760#comment-17807760
]
Jing Ge commented on FLINK-34135:
-
[~Sergey Nuyanzin] [~mapohl] FYI: [~jeyhunkarimov] is working on it.
> A number of ci failures with Access to the path
> '.../_work/_temp/containerHandlerInvoker.js' is denied.
> ---
>
> Key: FLINK-34135
> URL: https://issues.apache.org/jira/browse/FLINK-34135
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
>Reporter: Sergey Nuyanzin
>Assignee: Jeyhun Karimov
>Priority: Blocker
> Labels: test-stability
>
> There is a number of builds failing with something like
> {noformat}
> ##[error]Access to the path
> '/home/agent03/myagent/_work/_temp/containerHandlerInvoker.js' is denied.
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56490=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=fb588352-ef18-568d-b447-699986250ccb
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=554d7c3f-d38e-55f4-96b4-ada3a9cb7d6f=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=fa307d6d-91b1-5ab6-d460-ef50f552b1fe=1798d435-832b-51fe-a9ad-efb9abf4ab04=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=a1ac4ce4-9a4f-5fdb-3290-7e163fba19dc=e4c57254-ec06-5788-3f8e-5ad5dffb418e=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=2c3cbe13-dee0-5837-cf47-3053da9a8a78=56881383-f398-5091-6b3b-22a7eeb7cfa8=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=b0a398c0-685b-599c-eb57-c8c2a771138e=2d9c27d0-8dbb-5be9-7271-453f74f48ab3=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=162f98f7-8967-5f47-2782-a1e178ec2ad3=c9934c56-710d-5f85-d2b8-28ec1fd700ed=9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34135) A number of ci failures with Access to the path '.../_work/_temp/containerHandlerInvoker.js' is denied.
[
https://issues.apache.org/jira/browse/FLINK-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-34135:
---
Assignee: Jeyhun Karimov
> A number of ci failures with Access to the path
> '.../_work/_temp/containerHandlerInvoker.js' is denied.
> ---
>
> Key: FLINK-34135
> URL: https://issues.apache.org/jira/browse/FLINK-34135
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
>Reporter: Sergey Nuyanzin
>Assignee: Jeyhun Karimov
>Priority: Blocker
> Labels: test-stability
>
> There is a number of builds failing with something like
> {noformat}
> ##[error]Access to the path
> '/home/agent03/myagent/_work/_temp/containerHandlerInvoker.js' is denied.
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56490=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=fb588352-ef18-568d-b447-699986250ccb
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=554d7c3f-d38e-55f4-96b4-ada3a9cb7d6f=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=fa307d6d-91b1-5ab6-d460-ef50f552b1fe=1798d435-832b-51fe-a9ad-efb9abf4ab04=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=a1ac4ce4-9a4f-5fdb-3290-7e163fba19dc=e4c57254-ec06-5788-3f8e-5ad5dffb418e=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=2c3cbe13-dee0-5837-cf47-3053da9a8a78=56881383-f398-5091-6b3b-22a7eeb7cfa8=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=b0a398c0-685b-599c-eb57-c8c2a771138e=2d9c27d0-8dbb-5be9-7271-453f74f48ab3=9
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56481=logs=162f98f7-8967-5f47-2782-a1e178ec2ad3=c9934c56-710d-5f85-d2b8-28ec1fd700ed=9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-34098) Not enough Azure Pipeline CI runners available?
[ https://issues.apache.org/jira/browse/FLINK-34098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-34098: --- Assignee: Jeyhun Karimov > Not enough Azure Pipeline CI runners available? > --- > > Key: FLINK-34098 > URL: https://issues.apache.org/jira/browse/FLINK-34098 > Project: Flink > Issue Type: Bug > Components: Build System / CI >Affects Versions: 1.18.0, 1.17.2, 1.19.0 >Reporter: Matthias Pohl >Assignee: Jeyhun Karimov >Priority: Critical > > CI takes longer than usually. There might be an issue with the amount of > runners (on the Alibaba VMs)? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33842) Publish the Dockerfiles for the new release
[
https://issues.apache.org/jira/browse/FLINK-33842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33842:
Description:
Note: the official Dockerfiles fetch the binary distribution of the target
Flink version from an Apache mirror. After publishing the binary release
artifacts, mirrors can take some hours to start serving the new artifacts, so
you may want to wait to do this step until you are ready to continue with the
"Promote the release" steps in the follow-up Jira.
Follow the [release instructions in the flink-docker
repo|https://github.com/apache/flink-docker#release-workflow] to build the new
Dockerfiles and send an updated manifest to Docker Hub so the new images are
built and published.
Note: the flink-web PR has to be merged before the pull request to be opened on
the [{{official-images}}|https://github.com/docker-library/official-images]
repo.
h3. Expectations
* Dockerfiles in [flink-docker|https://github.com/apache/flink-docker] updated
for the new Flink release and pull request opened on the Docker official-images
with an updated manifest
was:
Note: the official Dockerfiles fetch the binary distribution of the target
Flink version from an Apache mirror. After publishing the binary release
artifacts, mirrors can take some hours to start serving the new artifacts, so
you may want to wait to do this step until you are ready to continue with the
"Promote the release" steps in the follow-up Jira.
Follow the [release instructions in the flink-docker
repo|https://github.com/apache/flink-docker#release-workflow] to build the new
Dockerfiles and send an updated manifest to Docker Hub so the new images are
built and published.
h3. Expectations
* Dockerfiles in [flink-docker|https://github.com/apache/flink-docker] updated
for the new Flink release and pull request opened on the Docker official-images
with an updated manifest
> Publish the Dockerfiles for the new release
> ---
>
> Key: FLINK-33842
> URL: https://issues.apache.org/jira/browse/FLINK-33842
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> Note: the official Dockerfiles fetch the binary distribution of the target
> Flink version from an Apache mirror. After publishing the binary release
> artifacts, mirrors can take some hours to start serving the new artifacts, so
> you may want to wait to do this step until you are ready to continue with the
> "Promote the release" steps in the follow-up Jira.
> Follow the [release instructions in the flink-docker
> repo|https://github.com/apache/flink-docker#release-workflow] to build the
> new Dockerfiles and send an updated manifest to Docker Hub so the new images
> are built and published.
> Note: the flink-web PR has to be merged before the pull request to be opened
> on the
> [{{official-images}}|https://github.com/docker-library/official-images] repo.
>
> h3. Expectations
> * Dockerfiles in [flink-docker|https://github.com/apache/flink-docker]
> updated for the new Flink release and pull request opened on the Docker
> official-images with an updated manifest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-33842) Publish the Dockerfiles for the new release
[ https://issues.apache.org/jira/browse/FLINK-33842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807624#comment-17807624 ] Jing Ge commented on FLINK-33842: - dev-1.18: df317cb99bdc28b9f0aafe8616aa075a07499fbf master: 627987997ca7ec86bcc3d80b26df58aa595b91af > Publish the Dockerfiles for the new release > --- > > Key: FLINK-33842 > URL: https://issues.apache.org/jira/browse/FLINK-33842 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > Labels: pull-request-available > > Note: the official Dockerfiles fetch the binary distribution of the target > Flink version from an Apache mirror. After publishing the binary release > artifacts, mirrors can take some hours to start serving the new artifacts, so > you may want to wait to do this step until you are ready to continue with the > "Promote the release" steps in the follow-up Jira. > Follow the [release instructions in the flink-docker > repo|https://github.com/apache/flink-docker#release-workflow] to build the > new Dockerfiles and send an updated manifest to Docker Hub so the new images > are built and published. > > > h3. Expectations > * Dockerfiles in [flink-docker|https://github.com/apache/flink-docker] > updated for the new Flink release and pull request opened on the Docker > official-images with an updated manifest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34075) Mark version as released in Jira (need PMC role)
[ https://issues.apache.org/jira/browse/FLINK-34075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807622#comment-17807622 ] Jing Ge commented on FLINK-34075: - Thanks! > Mark version as released in Jira (need PMC role) > > > Key: FLINK-34075 > URL: https://issues.apache.org/jira/browse/FLINK-34075 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Qingsheng Ren >Priority: Major > Fix For: 1.18.1 > > > In JIRA, inside [version > management|https://issues.apache.org/jira/plugins/servlet/project-config/FLINK/versions], > hover over the current release and a settings menu will appear. Click > Release, and select today’s date. > (Note: Only PMC members have access to the project administration. If you do > not have access, ask on the mailing list for assistance.) > > > h3. Expectations > * Release tagged in the source code repository > * Release version finalized in JIRA. (Note: Not all committers have > administrator access to JIRA. If you end up getting permissions errors ask on > the mailing list for assistance) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33844) Update japicmp configuration
[
https://issues.apache.org/jira/browse/FLINK-33844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33844:
Fix Version/s: 1.18.2
(was: 1.18.1)
> Update japicmp configuration
>
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.2
>
>
> Update the japicmp reference version and wipe exclusions / enable API
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see
> below).
> For a new major release (x.y.0), run the same command also on the master
> branch for updating the japicmp reference version and removing out-dated
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central.
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for
> $RELEASE_VERSION" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33844) Update japicmp configuration
[
https://issues.apache.org/jira/browse/FLINK-33844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33844:
Affects Version/s: (was: 1.18.0)
> Update japicmp configuration
>
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.1
>
>
> Update the japicmp reference version and wipe exclusions / enable API
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see
> below).
> For a new major release (x.y.0), run the same command also on the master
> branch for updating the japicmp reference version and removing out-dated
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central.
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for
> $RELEASE_VERSION" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33844) Update japicmp configuration
[
https://issues.apache.org/jira/browse/FLINK-33844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33844:
Fix Version/s: 1.18.1
> Update japicmp configuration
>
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.1
>
>
> Update the japicmp reference version and wipe exclusions / enable API
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see
> below).
> For a new major release (x.y.0), run the same command also on the master
> branch for updating the japicmp reference version and removing out-dated
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central.
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for
> $RELEASE_VERSION" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
