date:20210722



 [ 
https://issues.apache.org/jira/browse/FLINK-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Wysakowicz updated FLINK-23478:
-
Issue Type: Bug  (was: Improvement)

> KubernetesSharedInformerITCase.testWatchWithBlockHandler fails on Azure
> ---
>
> Key: FLINK-23478
> URL: https://issues.apache.org/jira/browse/FLINK-23478
> Project: Flink
>  Issue Type: Bug
>  Components: Deployment / Kubernetes
>Affects Versions: 1.14.0
>Reporter: Dawid Wysakowicz
>Priority: Major
>  Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20864=logs=c88eea3b-64a0-564d-0031-9fdcd7b8abee=070ff179-953e-5bda-71fa-d6599415701c=3190
> {code}
> Jul 23 04:41:49 java.util.concurrent.ExecutionException: 
> java.lang.AssertionError
> Jul 23 04:41:49   at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
> Jul 23 04:41:49   at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928)
> Jul 23 04:41:49   at 
> org.apache.flink.kubernetes.kubeclient.resources.KubernetesSharedInformerITCase.testWatchWithBlockHandler(KubernetesSharedInformerITCase.java:140)
> Jul 23 04:41:49   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
> Jul 23 04:41:49   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Jul 23 04:41:49   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Jul 23 04:41:49   at java.lang.reflect.Method.invoke(Method.java:498)
> Jul 23 04:41:49   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> Jul 23 04:41:49   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> Jul 23 04:41:49   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> Jul 23 04:41:49   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> Jul 23 04:41:49   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> Jul 23 04:41:49   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> Jul 23 04:41:49   at 
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> Jul 23 04:41:49   at 
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Jul 23 04:41:49   at 
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> Jul 23 04:41:49   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> Jul 23 04:41:49   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> Jul 23 04:41:49   at 
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> Jul 23 04:41:49   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Jul 23 04:41:49   at 
> org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> Jul 23 04:41:49   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> Jul 23 04:41:49 Caused by: java.lang.AssertionError
> Jul 23 04:41:49

[jira] [Created] (FLINK-23479) IncrementalAggregateJsonPlanTest.testIncrementalAggregateWithSumCountDistinctAndRetraction fail

Dawid Wysakowicz created FLINK-23479:


 Summary: 
IncrementalAggregateJsonPlanTest.testIncrementalAggregateWithSumCountDistinctAndRetraction
 fail
 Key: FLINK-23479
 URL: https://issues.apache.org/jira/browse/FLINK-23479
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Affects Versions: 1.14.0
Reporter: Dawid Wysakowicz


https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20864=logs=0c940707-2659-5648-cbe6-a1ad63045f0a=075c2716-8010-5565-fe08-3c4bb45824a4=8904

{code}
Jul 23 04:21:56 [ERROR] 
testIncrementalAggregateWithSumCountDistinctAndRetraction(org.apache.flink.table.planner.plan.nodes.exec.stream.IncrementalAggregateJsonPlanTest)
  Time elapsed: 0.067 s  <<< FAILURE!
Jul 23 04:21:56 org.junit.ComparisonFailure:

[jira] [Created] (FLINK-23478) KubernetesSharedInformerITCase.testWatchWithBlockHandler fails on Azure

Dawid Wysakowicz created FLINK-23478:


 Summary: KubernetesSharedInformerITCase.testWatchWithBlockHandler 
fails on Azure
 Key: FLINK-23478
 URL: https://issues.apache.org/jira/browse/FLINK-23478
 Project: Flink
  Issue Type: Improvement
  Components: Deployment / Kubernetes
Affects Versions: 1.14.0
Reporter: Dawid Wysakowicz


https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20864=logs=c88eea3b-64a0-564d-0031-9fdcd7b8abee=070ff179-953e-5bda-71fa-d6599415701c=3190

{code}
Jul 23 04:41:49 java.util.concurrent.ExecutionException: 
java.lang.AssertionError
Jul 23 04:41:49 at 
java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
Jul 23 04:41:49 at 
java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928)
Jul 23 04:41:49 at 
org.apache.flink.kubernetes.kubeclient.resources.KubernetesSharedInformerITCase.testWatchWithBlockHandler(KubernetesSharedInformerITCase.java:140)
Jul 23 04:41:49 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
Jul 23 04:41:49 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Jul 23 04:41:49 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Jul 23 04:41:49 at java.lang.reflect.Method.invoke(Method.java:498)
Jul 23 04:41:49 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
Jul 23 04:41:49 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
Jul 23 04:41:49 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
Jul 23 04:41:49 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
Jul 23 04:41:49 at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
Jul 23 04:41:49 at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
Jul 23 04:41:49 at 
org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
Jul 23 04:41:49 at 
org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
Jul 23 04:41:49 at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
Jul 23 04:41:49 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
Jul 23 04:41:49 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
Jul 23 04:41:49 at 
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
Jul 23 04:41:49 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
Jul 23 04:41:49 at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
Jul 23 04:41:49 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
Jul 23 04:41:49 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
Jul 23 04:41:49 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
Jul 23 04:41:49 at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
Jul 23 04:41:49 at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
Jul 23 04:41:49 at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
Jul 23 04:41:49 at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
Jul 23 04:41:49 at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Jul 23 04:41:49 Caused by: java.lang.AssertionError
Jul 23 04:41:49 at org.junit.Assert.fail(Assert.java:87)
Jul 23 04:41:49 at org.junit.Assert.assertTrue(Assert.java:42)
Jul 23 04:41:49 at org.junit.Assert.assertTrue(Assert.java:53)
Jul 23 04:41:49 at

[jira] [Reopened] (FLINK-9925) ClientTest.testSimpleRequests fails on Travis



 [ 
https://issues.apache.org/jira/browse/FLINK-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Wysakowicz reopened FLINK-9925:
-

1.13: 
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20857=logs=ba53eb01-1462-56a3-8e98-0dd97fbcaab5=bfbc6239-57a0-5db0-63f3-41551b4f7d51=14818

> ClientTest.testSimpleRequests fails on Travis
> -
>
> Key: FLINK-9925
> URL: https://issues.apache.org/jira/browse/FLINK-9925
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Queryable State, Tests
>Affects Versions: 1.7.0
>Reporter: Till Rohrmann
>Priority: Critical
>  Labels: test-stability
>
> {{ClientTest.testSimpleRequests}} fails on Travis with an {{AssertionError}}: 
> https://api.travis-ci.org/v3/job/405690023/log.txt



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (FLINK-17274) Maven: Premature end of Content-Length delimited message body



[ 
https://issues.apache.org/jira/browse/FLINK-17274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385959#comment-17385959
 ] 

Dawid Wysakowicz commented on FLINK-17274:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20857=logs=fc5181b0-e452-5c8f-68de-1097947f6483=62110053-334f-5295-a0ab-80dd7e2babbf=1626

> Maven: Premature end of Content-Length delimited message body
> -
>
> Key: FLINK-17274
> URL: https://issues.apache.org/jira/browse/FLINK-17274
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / Azure Pipelines
>Affects Versions: 1.14.0
>Reporter: Robert Metzger
>Priority: Major
>  Labels: auto-deprioritized-critical, test-stability
>
> CI: 
> https://dev.azure.com/rmetzger/Flink/_build/results?buildId=7786=logs=52b61abe-a3cc-5bde-cc35-1bbe89bb7df5=54421a62-0c80-5aad-3319-094ff69180bb
> {code}
> [ERROR] Failed to execute goal on project 
> flink-connector-elasticsearch7_2.11: Could not resolve dependencies for 
> project 
> org.apache.flink:flink-connector-elasticsearch7_2.11:jar:1.11-SNAPSHOT: Could 
> not transfer artifact org.apache.lucene:lucene-sandbox:jar:8.3.0 from/to 
> alicloud-mvn-mirror 
> (http://mavenmirror.alicloud.dak8s.net:/repository/maven-central/): GET 
> request of: org/apache/lucene/lucene-sandbox/8.3.0/lucene-sandbox-8.3.0.jar 
> from alicloud-mvn-mirror failed: Premature end of Content-Length delimited 
> message body (expected: 289920; received: 239832 -> [Help 1]
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (FLINK-20928) KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete:189->pollUntil:270 » Timeout



[ 
https://issues.apache.org/jira/browse/FLINK-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385956#comment-17385956
 ] 

Dawid Wysakowicz commented on FLINK-20928:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=72d4811f-9f0d-5fd0-014a-0bc26b72b642=e424005a-b16e-540f-196d-da062cc19bdf=6837

> KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete:189->pollUntil:270 
> » Timeout
> ---
>
> Key: FLINK-20928
> URL: https://issues.apache.org/jira/browse/FLINK-20928
> Project: Flink
>  Issue Type: Bug
>  Components: Connectors / Kafka
>Affects Versions: 1.13.0
>Reporter: Robert Metzger
>Priority: Major
>  Labels: auto-deprioritized-critical, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=11861=logs=c5f0071e-1851-543e-9a45-9ac140befc32=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5
> {code}
> [ERROR] Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
> 93.992 s <<< FAILURE! - in 
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest
> [ERROR] 
> testOffsetCommitOnCheckpointComplete(org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest)
>   Time elapsed: 60.086 s  <<< ERROR!
> java.util.concurrent.TimeoutException: The offset commit did not finish 
> before timeout.
>   at 
> org.apache.flink.core.testutils.CommonTestUtils.waitUtil(CommonTestUtils.java:210)
>   at 
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest.pollUntil(KafkaSourceReaderTest.java:270)
>   at 
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete(KafkaSourceReaderTest.java:189)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-20928) KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete:189->pollUntil:270 » Timeout



 [ 
https://issues.apache.org/jira/browse/FLINK-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Wysakowicz updated FLINK-20928:
-
Priority: Critical  (was: Major)

> KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete:189->pollUntil:270 
> » Timeout
> ---
>
> Key: FLINK-20928
> URL: https://issues.apache.org/jira/browse/FLINK-20928
> Project: Flink
>  Issue Type: Bug
>  Components: Connectors / Kafka
>Affects Versions: 1.13.0
>Reporter: Robert Metzger
>Priority: Critical
>  Labels: auto-deprioritized-critical, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=11861=logs=c5f0071e-1851-543e-9a45-9ac140befc32=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5
> {code}
> [ERROR] Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
> 93.992 s <<< FAILURE! - in 
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest
> [ERROR] 
> testOffsetCommitOnCheckpointComplete(org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest)
>   Time elapsed: 60.086 s  <<< ERROR!
> java.util.concurrent.TimeoutException: The offset commit did not finish 
> before timeout.
>   at 
> org.apache.flink.core.testutils.CommonTestUtils.waitUtil(CommonTestUtils.java:210)
>   at 
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest.pollUntil(KafkaSourceReaderTest.java:270)
>   at 
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete(KafkaSourceReaderTest.java:189)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] Airblader commented on pull request #16482: [FLINK-23369][docs][connector-hive][connector-kafka] Improve config options by using enums



Airblader commented on pull request #16482:
URL: https://github.com/apache/flink/pull/16482#issuecomment-885414506


   @flinkbot run azure


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16577: [FLINK-22861][table-planner-blink] Fix return value deduction of TIMESTAMPADD function



flinkbot edited a comment on pull request #16577:
URL: https://github.com/apache/flink/pull/16577#issuecomment-885401090


   
   ## CI report:
   
   * de0cd54961872f725bacc809cb1050823c704066 Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20868)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16575: [WIP][FLINK-23139][state] Add TaskStateRegistry



flinkbot edited a comment on pull request #16575:
URL: https://github.com/apache/flink/pull/16575#issuecomment-885295771


   
   ## CI report:
   
   * 74de0f3d61a1483e5e19cfc7d10369280c4cc82b Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20860)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16352: [FLINK-23102][runtime] Accessing FlameGraphs while not being enabled …



flinkbot edited a comment on pull request #16352:
URL: https://github.com/apache/flink/pull/16352#issuecomment-872812232


   
   ## CI report:
   
   * d438f5b58ca69878b66e0532bce4aeee44d68ff4 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20829)
 
   * 0f04da18a3c6c158a829d8d11ae87e8b6e5d4cbf UNKNOWN
   * c1b7febe3755a18b9a7058b357768ac90c0165a7 Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20867)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Issue Comment Deleted] (FLINK-23476) Snapshot deployments are broken



 [ 
https://issues.apache.org/jira/browse/FLINK-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Wysakowicz updated FLINK-23476:
-
Comment: was deleted

(was: 
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=585d8b77-fa33-51bc-8163-03e54ba9ce5b=5bcbcade-2929-53ee-0d97-1b2bc015247a)

> Snapshot deployments are broken
> ---
>
> Key: FLINK-23476
> URL: https://issues.apache.org/jira/browse/FLINK-23476
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / Azure Pipelines
>Affects Versions: 1.14.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Major
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=eca6b3a6-1600-56cc-916a-c549b3cde3ff=e9844b5e-5aa3-546b-6c3e-5395c7c0cac7
> {code}
> [ERROR] 'dependencies.dependency.version' for 
> com.typesafe.akka:akka-testkit_2.11:jar must be a valid version but is 
> '${akka.version}'. @ line 1212, column 15
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (FLINK-23476) Snapshot deployments are broken



[ 
https://issues.apache.org/jira/browse/FLINK-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385953#comment-17385953
 ] 

Dawid Wysakowicz commented on FLINK-23476:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=eca6b3a6-1600-56cc-916a-c549b3cde3ff=e9844b5e-5aa3-546b-6c3e-5395c7c0cac7

> Snapshot deployments are broken
> ---
>
> Key: FLINK-23476
> URL: https://issues.apache.org/jira/browse/FLINK-23476
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / Azure Pipelines
>Affects Versions: 1.14.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Major
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=eca6b3a6-1600-56cc-916a-c549b3cde3ff=e9844b5e-5aa3-546b-6c3e-5395c7c0cac7
> {code}
> [ERROR] 'dependencies.dependency.version' for 
> com.typesafe.akka:akka-testkit_2.11:jar must be a valid version but is 
> '${akka.version}'. @ line 1212, column 15
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (FLINK-23476) Snapshot deployments are broken



[ 
https://issues.apache.org/jira/browse/FLINK-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385951#comment-17385951
 ] 

Dawid Wysakowicz commented on FLINK-23476:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=585d8b77-fa33-51bc-8163-03e54ba9ce5b=5bcbcade-2929-53ee-0d97-1b2bc015247a

> Snapshot deployments are broken
> ---
>
> Key: FLINK-23476
> URL: https://issues.apache.org/jira/browse/FLINK-23476
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / Azure Pipelines
>Affects Versions: 1.14.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Major
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=eca6b3a6-1600-56cc-916a-c549b3cde3ff=e9844b5e-5aa3-546b-6c3e-5395c7c0cac7
> {code}
> [ERROR] 'dependencies.dependency.version' for 
> com.typesafe.akka:akka-testkit_2.11:jar must be a valid version but is 
> '${akka.version}'. @ line 1212, column 15
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (FLINK-21538) Elasticsearch6DynamicSinkITCase.testWritingDocuments fails when submitting job



[ 
https://issues.apache.org/jira/browse/FLINK-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385950#comment-17385950
 ] 

Dawid Wysakowicz commented on FLINK-21538:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20852=logs=d44f43ce-542c-597d-bf94-b0718c71e5e8=34f486e1-e1e4-5dd2-9c06-bfdd9b9c74a8=12108


> Elasticsearch6DynamicSinkITCase.testWritingDocuments fails when submitting job
> --
>
> Key: FLINK-21538
> URL: https://issues.apache.org/jira/browse/FLINK-21538
> Project: Flink
>  Issue Type: Bug
>  Components: Connectors / ElasticSearch, Runtime / Coordination
>Affects Versions: 1.12.1, 1.13.0
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=13868=logs=3d12d40f-c62d-5ec4-6acc-0efe94cc3e89=5d6e4255-0ea8-5e2a-f52c-c881b7872361
> {code}
> 2021-02-27T00:16:06.9493539Z 
> org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
> 2021-02-27T00:16:06.9494494Z  at 
> org.apache.flink.runtime.jobmaster.JobResult.toJobExecutionResult(JobResult.java:144)
> 2021-02-27T00:16:06.9495733Z  at 
> org.apache.flink.runtime.minicluster.MiniClusterJobClient.lambda$getJobExecutionResult$2(MiniClusterJobClient.java:117)
> 2021-02-27T00:16:06.9496596Z  at 
> java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:616)
> 2021-02-27T00:16:06.9497354Z  at 
> java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591)
> 2021-02-27T00:16:06.9525795Z  at 
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
> 2021-02-27T00:16:06.9526744Z  at 
> java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
> 2021-02-27T00:16:06.9527784Z  at 
> org.apache.flink.runtime.rpc.akka.AkkaInvocationHandler.lambda$invokeRpc$0(AkkaInvocationHandler.java:237)
> 2021-02-27T00:16:06.9528552Z  at 
> java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
> 2021-02-27T00:16:06.9529271Z  at 
> java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
> 2021-02-27T00:16:06.9530013Z  at 
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
> 2021-02-27T00:16:06.9530482Z  at 
> java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
> 2021-02-27T00:16:06.9531068Z  at 
> org.apache.flink.runtime.concurrent.FutureUtils$1.onComplete(FutureUtils.java:1046)
> 2021-02-27T00:16:06.9531544Z  at 
> akka.dispatch.OnComplete.internal(Future.scala:264)
> 2021-02-27T00:16:06.9531908Z  at 
> akka.dispatch.OnComplete.internal(Future.scala:261)
> 2021-02-27T00:16:06.9532449Z  at 
> akka.dispatch.japi$CallbackBridge.apply(Future.scala:191)
> 2021-02-27T00:16:06.9532860Z  at 
> akka.dispatch.japi$CallbackBridge.apply(Future.scala:188)
> 2021-02-27T00:16:06.9533245Z  at 
> scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
> 2021-02-27T00:16:06.9533721Z  at 
> org.apache.flink.runtime.concurrent.Executors$DirectExecutionContext.execute(Executors.java:73)
> 2021-02-27T00:16:06.9534225Z  at 
> scala.concurrent.impl.CallbackRunnable.executeWithValue(Promise.scala:68)
> 2021-02-27T00:16:06.9534697Z  at 
> scala.concurrent.impl.Promise$DefaultPromise.$anonfun$tryComplete$1(Promise.scala:284)
> 2021-02-27T00:16:06.9535217Z  at 
> scala.concurrent.impl.Promise$DefaultPromise.$anonfun$tryComplete$1$adapted(Promise.scala:284)
> 2021-02-27T00:16:06.9535718Z  at 
> scala.concurrent.impl.Promise$DefaultPromise.tryComplete(Promise.scala:284)
> 2021-02-27T00:16:06.9536127Z  at 
> akka.pattern.PromiseActorRef.$bang(AskSupport.scala:573)
> 2021-02-27T00:16:06.9536861Z  at 
> akka.pattern.PipeToSupport$PipeableFuture$$anonfun$pipeTo$1.applyOrElse(PipeToSupport.scala:22)
> 2021-02-27T00:16:06.9537394Z  at 
> akka.pattern.PipeToSupport$PipeableFuture$$anonfun$pipeTo$1.applyOrElse(PipeToSupport.scala:21)
> 2021-02-27T00:16:06.9537916Z  at 
> scala.concurrent.Future.$anonfun$andThen$1(Future.scala:532)
> 2021-02-27T00:16:06.9605804Z  at 
> scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:29)
> 2021-02-27T00:16:06.9606794Z  at 
> scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:29)
> 2021-02-27T00:16:06.9607642Z  at 
> scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
> 2021-02-27T00:16:06.9608419Z  at 
> akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
> 2021-02-27T00:16:06.9609252Z  at 
> akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
> 2021-02-27T00:16:06.9610024Z  at 
> scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
>

[jira] [Updated] (FLINK-23097) 'Queryable state (rocksdb) with TM restart end-to-end test' fails on azure



 [ 
https://issues.apache.org/jira/browse/FLINK-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Wysakowicz updated FLINK-23097:
-
Affects Version/s: 1.12.4

> 'Queryable state (rocksdb) with TM restart end-to-end test' fails on azure
> --
>
> Key: FLINK-23097
> URL: https://issues.apache.org/jira/browse/FLINK-23097
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Queryable State
>Affects Versions: 1.14.0, 1.12.4
>Reporter: Dawid Wysakowicz
>Priority: Major
>  Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=19310=logs=c88eea3b-64a0-564d-0031-9fdcd7b8abee=ff888d9b-cd34-53cc-d90f-3e446d355529=12333
> {code}
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> Jun 22 14:04:55 MapState has 22 entries
> Jun 22 14:04:56 TaskManager 422719 killed.
> Jun 22 14:04:56 Number of running task managers 1 is not yet 0.
> Jun 22 14:05:00 Number of running task managers 1 is not yet 0.
> Jun 22 14:05:04 Number of running task managers 1 is not yet 0.
> Jun 22 14:05:08 Number of running task managers has reached 0.
> Jun 22 14:05:08 Latest snapshot count was 42
> Jun 22 14:05:09 Starting taskexecutor daemon on host fv-az68-17.
> Jun 22 14:05:09 Number of running task managers 0 is not yet 1.
> Jun 22 14:05:13 Number of running task managers has reached 1.
> Jun 22 14:05:15 Job (5b515e0f9168e338d1645bf2e9f92820) is running.
> Jun 22 14:05:15 Starting to wait for completion of 18 checkpoints
> Jun 22 14:05:15 13/18 completed checkpoints
> Jun 22 14:05:17 13/18 completed checkpoints
> Jun 22 14:05:19 17/18 completed checkpoints
> Jun 22 14:05:21 17/18 completed checkpoints
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> Jun 22 14:05:24 after: 40
> Jun 22 14:05:24 An error occurred
> Jun 22 14:05:24 [FAIL] Test script contains errors.
> Jun 22 14:05:24 Checking of logs skipped.
> Jun 22 14:05:24 
> Jun 22 14:05:24 [FAIL] 'Queryable state (rocksdb) with TM restart end-to-end 
> test' failed after 0 minutes and 50 seconds! Test exited with exit code 1
> Jun 22 14:05:24 
> 14:05:24 ##[group]Environment Information
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (FLINK-23097) 'Queryable state (rocksdb) with TM restart end-to-end test' fails on azure



[ 
https://issues.apache.org/jira/browse/FLINK-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385949#comment-17385949
 ] 

Dawid Wysakowicz commented on FLINK-23097:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20851=logs=c88eea3b-64a0-564d-0031-9fdcd7b8abee=ff888d9b-cd34-53cc-d90f-3e446d355529=11938

> 'Queryable state (rocksdb) with TM restart end-to-end test' fails on azure
> --
>
> Key: FLINK-23097
> URL: https://issues.apache.org/jira/browse/FLINK-23097
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Queryable State
>Affects Versions: 1.14.0
>Reporter: Dawid Wysakowicz
>Priority: Major
>  Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=19310=logs=c88eea3b-64a0-564d-0031-9fdcd7b8abee=ff888d9b-cd34-53cc-d90f-3e446d355529=12333
> {code}
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> Jun 22 14:04:55 MapState has 22 entries
> Jun 22 14:04:56 TaskManager 422719 killed.
> Jun 22 14:04:56 Number of running task managers 1 is not yet 0.
> Jun 22 14:05:00 Number of running task managers 1 is not yet 0.
> Jun 22 14:05:04 Number of running task managers 1 is not yet 0.
> Jun 22 14:05:08 Number of running task managers has reached 0.
> Jun 22 14:05:08 Latest snapshot count was 42
> Jun 22 14:05:09 Starting taskexecutor daemon on host fv-az68-17.
> Jun 22 14:05:09 Number of running task managers 0 is not yet 1.
> Jun 22 14:05:13 Number of running task managers has reached 1.
> Jun 22 14:05:15 Job (5b515e0f9168e338d1645bf2e9f92820) is running.
> Jun 22 14:05:15 Starting to wait for completion of 18 checkpoints
> Jun 22 14:05:15 13/18 completed checkpoints
> Jun 22 14:05:17 13/18 completed checkpoints
> Jun 22 14:05:19 17/18 completed checkpoints
> Jun 22 14:05:21 17/18 completed checkpoints
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> Jun 22 14:05:24 after: 40
> Jun 22 14:05:24 An error occurred
> Jun 22 14:05:24 [FAIL] Test script contains errors.
> Jun 22 14:05:24 Checking of logs skipped.
> Jun 22 14:05:24 
> Jun 22 14:05:24 [FAIL] 'Queryable state (rocksdb) with TM restart end-to-end 
> test' failed after 0 minutes and 50 seconds! Test exited with exit code 1
> Jun 22 14:05:24 
> 14:05:24 ##[group]Environment Information
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (FLINK-23477) wasbs/s3 FileSystem support

2021-07-22 Thread Harshvardhan (Jira)

Harshvardhan created FLINK-23477:


 Summary: wasbs/s3 FileSystem support
 Key: FLINK-23477
 URL: https://issues.apache.org/jira/browse/FLINK-23477
 Project: Flink
  Issue Type: Bug
  Components: Deployment / Kubernetes
Affects Versions: 1.13.0
Reporter: Harshvardhan


Flink is unable to identify Azure and AWS FileSystem plugins independent of 
Hadoop APIs on Native Kubernetes on Azure.

Plugins added as libraries are kept under 
/opt/flink/plugins/flink-s3-fs-hadoop.jar/flink-s3-fs-hadoop.jar

The Flink is unable to read the plugins.

Same issue even after enabling dependencies in YAML file as 
'ENABLE_BUILT_IN_PLUGINS'.

 

Reference Documentation : [here | 
https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/deployment/filesystems/plugins/]

Exception:

{{}}

{{Caused by: org.apache.flink.core.fs.UnsupportedFileSystemSchemeException: 
Could not find a file system implementation for scheme 's3'. The scheme is 
directly supported byFlink through the following plugins: flink-s3-fs-hadoop, 
flink-s3-fs-presto. Please ensure that each plugin resides within its own 
subfolder within the plugins directory.See 
https://ci.apache.org/projects/flink/flink-docs-stable/ops/plugins.html for 
more information. If you want to use a Hadoop file system for that scheme, 
please add the scheme to the configuration fs.allowed-fallback-filesystems. For 
a full list of supported file systems, please see 
https://ci.apache.org/projects/flink/flink-docs-stable/ops/filesystems/.at 
org.apache.flink.core.fs.FileSystem.getUnguardedFileSystem(FileSystem.java:513)at
 org.apache.flink.core.fs.FileSystem.get(FileSystem.java:407)at 
org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction.run(ContinuousFileMonitoringFunction.java:214)at
 
org.apache.flink.streaming.api.operators.StreamSource.run(StreamSource.java:110)at
 
org.apache.flink.streaming.api.operators.StreamSource.run(StreamSource.java:66)at
 
org.apache.flink.streaming.runtime.tasks.SourceStreamTask$LegacySourceFunctionThread.run(SourceStreamTask.java:269)}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot commented on pull request #16577: [FLINK-22861][table-planner-blink] Fix return value deduction of TIMESTAMPADD function



flinkbot commented on pull request #16577:
URL: https://github.com/apache/flink/pull/16577#issuecomment-885401090


   
   ## CI report:
   
   * de0cd54961872f725bacc809cb1050823c704066 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16352: [FLINK-23102][runtime] Accessing FlameGraphs while not being enabled …



flinkbot edited a comment on pull request #16352:
URL: https://github.com/apache/flink/pull/16352#issuecomment-872812232


   
   ## CI report:
   
   * d438f5b58ca69878b66e0532bce4aeee44d68ff4 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20829)
 
   * 0f04da18a3c6c158a829d8d11ae87e8b6e5d4cbf UNKNOWN
   * c1b7febe3755a18b9a7058b357768ac90c0165a7 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot commented on pull request #16577: [FLINK-22861][table-planner-blink] Fix return value deduction of TIMESTAMPADD function



flinkbot commented on pull request #16577:
URL: https://github.com/apache/flink/pull/16577#issuecomment-885397779


   Thanks a lot for your contribution to the Apache Flink project. I'm the 
@flinkbot. I help the community
   to review your pull request. We will use this comment to track the progress 
of the review.
   
   
   ## Automated Checks
   Last check on commit de0cd54961872f725bacc809cb1050823c704066 (Fri Jul 23 
04:52:15 UTC 2021)
   
   **Warnings:**
* No documentation files were touched! Remember to keep the Flink docs up 
to date!
   
   
   Mention the bot in a comment to re-run the automated checks.
   ## Review Progress
   
   * ❓ 1. The [description] looks good.
   * ❓ 2. There is [consensus] that the contribution should go into to Flink.
   * ❓ 3. Needs [attention] from.
   * ❓ 4. The change fits into the overall [architecture].
   * ❓ 5. Overall code [quality] is good.
   
   Please see the [Pull Request Review 
Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full 
explanation of the review process.
The Bot is tracking the review progress through labels. Labels are applied 
according to the order of the review items. For consensus, approval by a Flink 
committer of PMC member is required Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot approve description` to approve one or more aspects (aspects: 
`description`, `consensus`, `architecture` and `quality`)
- `@flinkbot approve all` to approve all aspects
- `@flinkbot approve-until architecture` to approve everything until 
`architecture`
- `@flinkbot attention @username1 [@username2 ..]` to require somebody's 
attention
- `@flinkbot disapprove architecture` to remove an approval you gave earlier
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] tsreaper opened a new pull request #16577: [FLINK-22861][table-planner-blink] Fix return value deduction of TIMESTAMPADD function



tsreaper opened a new pull request #16577:
URL: https://github.com/apache/flink/pull/16577


   (This PR is cherry-picked from #16511)
   
   ## What is the purpose of the change
   
   Currently `TIMESTAMPADD(MINUTE, 10, CURRENT_TIMESTAMP)` will be deduced as 
`timestamp` type. However this should be `timestamp with local time zone` type. 
With this incorrect type, code generation will refuse to work.
   
   This PR fixes this issue by copying and modifying the corresponding classes 
from Calcite.
   
   ## Brief change log
   
- Fix return value deduction of TIMESTAMPADD function
   
   ## Verifying this change
   
   This change added tests and can be verified by running the added tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
 - Dependencies (does it add or upgrade a dependency): no
 - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
 - The serializers: no
 - The runtime per-record code paths (performance sensitive): no
 - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
 - The S3 file system connector: no
   
   ## Documentation
   
 - Does this pull request introduce a new feature? no
 - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16576: [FLINK-23463][doc] Replace the tag with ShortCodes in document



flinkbot edited a comment on pull request #16576:
URL: https://github.com/apache/flink/pull/16576#issuecomment-885383955


   
   ## CI report:
   
   * f937074853baf861a1c4bc049e79249b15b63005 Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20866)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16352: [FLINK-23102][runtime] Accessing FlameGraphs while not being enabled …



flinkbot edited a comment on pull request #16352:
URL: https://github.com/apache/flink/pull/16352#issuecomment-872812232


   
   ## CI report:
   
   * d438f5b58ca69878b66e0532bce4aeee44d68ff4 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20829)
 
   * 0f04da18a3c6c158a829d8d11ae87e8b6e5d4cbf UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] paul8263 commented on pull request #16352: [FLINK-23102][runtime] Accessing FlameGraphs while not being enabled …



paul8263 commented on pull request #16352:
URL: https://github.com/apache/flink/pull/16352#issuecomment-885392313


   Hi @zentol , I did the rebase and now it should be OK. Thank you for your 
advice.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot commented on pull request #16576: [FLINK-23463][doc] Replace the tag with ShortCodes in document



flinkbot commented on pull request #16576:
URL: https://github.com/apache/flink/pull/16576#issuecomment-885383955


   
   ## CI report:
   
   * f937074853baf861a1c4bc049e79249b15b63005 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16563: [FLINK-22540][sql-client] Remove Yaml environment file in SQL Client



flinkbot edited a comment on pull request #16563:
URL: https://github.com/apache/flink/pull/16563#issuecomment-884699874


   
   ## CI report:
   
   * ed52db259301f3eef523affcc45179f8537946aa Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20823)
 
   * 821aceafdd1a40911266c5be58a65a5f63fa535d Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20865)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (FLINK-23201) The check on alignmentDurationNanos seems to be too strict

2021-07-22 Thread Jingsong Lee (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jingsong Lee updated FLINK-23201:
-
Fix Version/s: (was: 1.12.6)
   1.12.5

> The check on alignmentDurationNanos seems to be too strict
> --
>
> Key: FLINK-23201
> URL: https://issues.apache.org/jira/browse/FLINK-23201
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Metrics
>Affects Versions: 1.12.2, 1.14.0, 1.13.1
>Reporter: Jun Qin
>Assignee: Anton Kalashnikov
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 1.14.0, 1.12.5, 1.13.3
>
>
> The check on alignmentDurationNanos seems to be too strict at the line:
> https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/CheckpointMetrics.java#L74
> This caused a job to fail when doing stop-with-savepoint. But doing savepoint 
> only without stop does not seem to be impacted by this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-22898) HiveParallelismInference limit return wrong parallelism

2021-07-22 Thread Jingsong Lee (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-22898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jingsong Lee updated FLINK-22898:
-
Fix Version/s: (was: 1.12.6)
   1.12.5

> HiveParallelismInference limit return wrong parallelism
> ---
>
> Key: FLINK-22898
> URL: https://issues.apache.org/jira/browse/FLINK-22898
> Project: Flink
>  Issue Type: Bug
>  Components: Table SQL / Ecosystem
>Reporter: Jingsong Lee
>Assignee: luoyuxia
>Priority: Major
>  Labels: auto-deprioritized-critical, pull-request-available
> Fix For: 1.14.0, 1.12.5, 1.13.3
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot commented on pull request #16576: [FLINK-23463][doc] Replace the tag with ShortCodes in document



flinkbot commented on pull request #16576:
URL: https://github.com/apache/flink/pull/16576#issuecomment-885377582


   Thanks a lot for your contribution to the Apache Flink project. I'm the 
@flinkbot. I help the community
   to review your pull request. We will use this comment to track the progress 
of the review.
   
   
   ## Automated Checks
   Last check on commit f937074853baf861a1c4bc049e79249b15b63005 (Fri Jul 23 
03:42:07 UTC 2021)
   
✅no warnings
   
   Mention the bot in a comment to re-run the automated checks.
   ## Review Progress
   
   * ❓ 1. The [description] looks good.
   * ❓ 2. There is [consensus] that the contribution should go into to Flink.
   * ❓ 3. Needs [attention] from.
   * ❓ 4. The change fits into the overall [architecture].
   * ❓ 5. Overall code [quality] is good.
   
   Please see the [Pull Request Review 
Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full 
explanation of the review process.
The Bot is tracking the review progress through labels. Labels are applied 
according to the order of the review items. For consensus, approval by a Flink 
committer of PMC member is required Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot approve description` to approve one or more aspects (aspects: 
`description`, `consensus`, `architecture` and `quality`)
- `@flinkbot approve all` to approve all aspects
- `@flinkbot approve-until architecture` to approve everything until 
`architecture`
- `@flinkbot attention @username1 [@username2 ..]` to require somebody's 
attention
- `@flinkbot disapprove architecture` to remove an approval you gave earlier
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (FLINK-22802) Bump Fabric8 Kubernetes Client to >= 5.X



[ 
https://issues.apache.org/jira/browse/FLINK-22802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385917#comment-17385917
 ] 

Yang Wang commented on FLINK-22802:
---

It does not have too many API breaking changes from 4.9.2 to 5.5.0 for fabric8 
Kubernetes client. I am just not very confident about the stability and trying 
to run more Flink on K8s workloads with various cases for long time.

> Bump Fabric8 Kubernetes Client to >= 5.X
> 
>
> Key: FLINK-22802
> URL: https://issues.apache.org/jira/browse/FLINK-22802
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes
>Affects Versions: 1.13.0, 1.13.1, 1.12.4
> Environment: Kubernetes 1.19/1.20 provided as part of Openshift 
> 4.6/4.7
> Flink 1.13.0 and 1.13.1-rc1
>Reporter: Enrique Lacal
>Assignee: Yang Wang
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.14.0
>
>
> Hi All, 
> Currently, Flink is using version 4.9.2 of the Fabric8 Kubernetes Client 
> which does not support new versions of the Kubernetes API such as 1.19 or 
> 1.20 as pointed out by their [Compatibility 
> Matrix|https://github.com/fabric8io/kubernetes-client#compatibility-matrix] 
> which is support in 5.4.0 or above.
> As far as I have seen in the Flink documentation, Flink supports `Kubernetes 
> >= 1.9.` but due to this dependency, it might not be the case. Is there a 
> plan to update this dependency?
> What is the plan moving forwards when new versions of Kubernetes are released?
> I am raising this because I have been testing Flink HA Session Cluster on 
> Kubernetes 1.19 and 1.20 and I have encountered some frequent errors that 
> force the JM pods to restart or even result in an unrecoverable state.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot edited a comment on pull request #16563: [FLINK-22540][sql-client] Remove Yaml environment file in SQL Client



flinkbot edited a comment on pull request #16563:
URL: https://github.com/apache/flink/pull/16563#issuecomment-884699874


   
   ## CI report:
   
   * ed52db259301f3eef523affcc45179f8537946aa Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20823)
 
   * 821aceafdd1a40911266c5be58a65a5f63fa535d UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (FLINK-22802) Bump Fabric8 Kubernetes Client to >= 5.X



 [ 
https://issues.apache.org/jira/browse/FLINK-22802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang updated FLINK-22802:
--
Fix Version/s: 1.14.0

> Bump Fabric8 Kubernetes Client to >= 5.X
> 
>
> Key: FLINK-22802
> URL: https://issues.apache.org/jira/browse/FLINK-22802
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes
>Affects Versions: 1.13.0, 1.13.1, 1.12.4
> Environment: Kubernetes 1.19/1.20 provided as part of Openshift 
> 4.6/4.7
> Flink 1.13.0 and 1.13.1-rc1
>Reporter: Enrique Lacal
>Assignee: Yang Wang
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.14.0
>
>
> Hi All, 
> Currently, Flink is using version 4.9.2 of the Fabric8 Kubernetes Client 
> which does not support new versions of the Kubernetes API such as 1.19 or 
> 1.20 as pointed out by their [Compatibility 
> Matrix|https://github.com/fabric8io/kubernetes-client#compatibility-matrix] 
> which is support in 5.4.0 or above.
> As far as I have seen in the Flink documentation, Flink supports `Kubernetes 
> >= 1.9.` but due to this dependency, it might not be the case. Is there a 
> plan to update this dependency?
> What is the plan moving forwards when new versions of Kubernetes are released?
> I am raising this because I have been testing Flink HA Session Cluster on 
> Kubernetes 1.19 and 1.20 and I have encountered some frequent errors that 
> force the JM pods to restart or even result in an unrecoverable state.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-23463) Replace the tag with ShortCodes in document

2021-07-22 Thread ASF GitHub Bot (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-23463:
---
Labels: pull-request-available  (was: )

> Replace the  tag with ShortCodes in document
> -
>
> Key: FLINK-23463
> URL: https://issues.apache.org/jira/browse/FLINK-23463
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.14.0
>Reporter: Yangze Guo
>Assignee: Yangze Guo
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In FLINK-22922, we migrate Flink website to hugo. At the moment, most of the 
> div tag in user doc is no long take effect. We need to replace them with the 
> ShortCodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] KarmaGYZ opened a new pull request #16576: [FLINK-23463][doc] Replace the tag with ShortCodes in document



KarmaGYZ opened a new pull request #16576:
URL: https://github.com/apache/flink/pull/16576


   
   
   ## What is the purpose of the change
   
   *(For example: This pull request makes task deployment go through the blob 
server, rather than through RPC. That way we avoid re-transferring them on each 
deployment (during recovery).)*
   
   
   ## Brief change log
   
   *(for example:)*
 - *The TaskInfo is stored in the blob store on job creation time as a 
persistent artifact*
 - *Deployments RPC transmits only the blob storage reference*
 - *TaskManagers retrieve the TaskInfo from the blob cache*
   
   
   ## Verifying this change
   
   *(Please pick either of the following options)*
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   *(or)*
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   *(or)*
   
   This change added tests and can be verified as follows:
   
   *(example:)*
 - *Added integration tests for end-to-end deployment with large payloads 
(100MB)*
 - *Extended integration test for recovery after master (JobManager) 
failure*
 - *Added test that validates that TaskInfo is transferred only once across 
recoveries*
 - *Manually verified the change by running a 4 node cluser with 2 
JobManagers and 4 TaskManagers, a stateful streaming program, and killing one 
JobManager and two TaskManagers during the execution, verifying that recovery 
happens correctly.*
   
   ## Does this pull request potentially affect one of the following parts:
   
 - Dependencies (does it add or upgrade a dependency): (yes / no)
 - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / no)
 - The serializers: (yes / no / don't know)
 - The runtime per-record code paths (performance sensitive): (yes / no / 
don't know)
 - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
 - The S3 file system connector: (yes / no / don't know)
   
   ## Documentation
   
 - Does this pull request introduce a new feature? (yes / no)
 - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] tsreaper commented on a change in pull request #16547: [FLINK-23423][docs-zh] Translate the page of "Elasticsearch Connector" into Chinese



tsreaper commented on a change in pull request #16547:
URL: https://github.com/apache/flink/pull/16547#discussion_r675277888



##
File path: docs/content.zh/docs/connectors/datastream/elasticsearch.md
##
@@ -51,29 +49,25 @@ of the Elasticsearch installation:
 {{< artifact flink-connector-elasticsearch6 withScalaVersion 
>}}
 
 
-7 and later versions
+7 及更高版本
 {{< artifact flink-connector-elasticsearch7 withScalaVersion 
>}}
 
   
 
 
-Note that the streaming connectors are currently not part of the binary
-distribution. See [here]({{< ref "docs/dev/datastream/project-configuration" 
>}}) for information
-about how to package the program with the libraries for cluster execution.
+请注意，流连接器目前不是二进制发行版的一部分。
+有关如何将程序和用于集群执行的库一起打包，参考[此处]({{< ref 
"docs/dev/datastream/project-configuration" >}})
 
-## Installing Elasticsearch
+## 安装 Elasticsearch
 
-Instructions for setting up an Elasticsearch cluster can be found
-[here](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html).
-Make sure to set and remember a cluster name. This must be set when
-creating an `ElasticsearchSink` for requesting document actions against your 
cluster.
+Elasticsearch 
集群的设置可以参考[此处](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html)。
+确保设置并记住集群名称。这是在创建 `ElasticsearchSink` 请求集群文档操作时必须要设置的。
 
-## Elasticsearch Sink
+## Elasticsearch 接收器

Review comment:
   保持“Sink”这个词，无需翻译为“接收器”。参见其它已翻译的 connector 文档，如 
[RabbitMQ](https://ci.apache.org/projects/flink/flink-docs-master/zh/docs/connectors/datastream/rabbitmq/#rabbitmq-sink)
 和 
[NiFi](https://ci.apache.org/projects/flink/flink-docs-master/zh/docs/connectors/datastream/rabbitmq/#rabbitmq-sink)，下文中的
 sink 也是如此。

##
File path: docs/content.zh/docs/connectors/datastream/elasticsearch.md
##
@@ -276,49 +270,37 @@ esSinkBuilder.setRestClientFactory(new RestClientFactory {
   }
 })
 
-// finally, build and add the sink to the job's pipeline
+// 最后，构建并添加接收器到作业管道中
 input.addSink(esSinkBuilder.build)
 ```
 {{< /tab >}}
 {{< /tabs >}}
 
-For Elasticsearch versions that still uses the now deprecated 
`TransportClient` to communicate
-with the Elasticsearch cluster (i.e., versions equal or below 5.x), note how a 
`Map` of `String`s
-is used to configure the `ElasticsearchSink`. This config map will be directly
-forwarded when creating the internally used `TransportClient`.
-The configuration keys are documented in the Elasticsearch documentation
-[here](https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html).
-Especially important is the `cluster.name` parameter that must correspond to
-the name of your cluster.
+对于仍然使用已被弃用的 `TransportClient` 和 Elasticsearch 集群通信的 Elasticsearch 版本 (即，小于或等于 
5.x 的版本)，
+请注意如何使用一个 `String` 类型的 `Map` 配置 `ElasticsearchSink`。在创建内部使用的 `TransportClient` 
时将直接转发此配置映射。
+配置键记录在[此处](https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html)的
 Elasticsearch 文档中。
+特别重要的是参数 `cluster.name` 必须和你的集群名称对应上。
 
-For Elasticsearch 6.x and above, internally, the `RestHighLevelClient` is used 
for cluster communication.
-By default, the connector uses the default configurations for the REST client. 
To have custom
-configuration for the REST client, users can provide a `RestClientFactory` 
implementation when 
-setting up the `ElasticsearchClient.Builder` that builds the sink.
+对于 Elasticsearch 6.x 及以上版本，内部使用 `RestHighLevelClient` 和集群通信。
+默认情况下，连接器使用 REST 客户端的默认配置。
+如果要使用自定义配置的 REST 客户端，用户可以在设置构建接收器的 `ElasticsearchClient.Builder` 时提供一个 
`RestClientFactory` 的实现。
 
-Also note that the example only demonstrates performing a single index
-request for each incoming element. Generally, the `ElasticsearchSinkFunction`
-can be used to perform multiple requests of different types (ex.,
-`DeleteRequest`, `UpdateRequest`, etc.). 
+另外注意，该示例仅演示了对每个传入的元素执行单个索引请求。
+通常，`ElasticsearchSinkFunction` 可用于执行多个不同类型的请求（例如 `DeleteRequest`、 
`UpdateRequest` 等）。
 
-Internally, each parallel instance of the Flink Elasticsearch Sink uses
-a `BulkProcessor` to send action requests to the cluster.
-This will buffer elements before sending them in bulk to the cluster. The 
`BulkProcessor`
-executes bulk requests one at a time, i.e. there will be no two concurrent
-flushes of the buffered actions in progress.
+在内部，Flink Elasticsearch 接收器的每个并行实例使用一个 `BulkProcessor` 向集群发送操作请求。
+这将使得元素在发送到集群之前进行批量缓存。
+`BulkProcessor` 一次执行一个批量请求，即不会存在两个并行刷新缓存的操作。
 
-### Elasticsearch Sinks and Fault Tolerance
+### Elasticsearch 接收器和容错
 
-With Flink’s checkpointing enabled, the Flink Elasticsearch Sink guarantees
-at-least-once delivery of action requests to Elasticsearch clusters. It does
-so by waiting for all pending action requests in the `BulkProcessor` at the
-time of checkpoints. This effectively assures that all requests before the
-checkpoint was triggered have been successfully acknowledged by Elasticsearch, 
before
-proceeding to process more records sent to the sink.
+启用

[jira] [Closed] (FLINK-23467) Remove the usage of the yaml file in pyflink e2e test

2021-07-22 Thread Jark Wu (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jark Wu closed FLINK-23467.
---
Resolution: Fixed

Fixed in master: ad5dcb2bdebecc59380672da652420da3ef09c6a

> Remove the usage of the yaml file in pyflink e2e test
> -
>
> Key: FLINK-23467
> URL: https://issues.apache.org/jira/browse/FLINK-23467
> Project: Flink
>  Issue Type: Improvement
>  Components: Tests
>Affects Versions: 1.14.0
>Reporter: Shengkai Fang
>Assignee: Shengkai Fang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] wuchong merged pull request #16574: [FLINK-23467][e2e] Remove usage of the YAML file in pyflink.sh



wuchong merged pull request #16574:
URL: https://github.com/apache/flink/pull/16574


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (FLINK-23418) 'Run kubernetes application HA test' fail on Azure



[ 
https://issues.apache.org/jira/browse/FLINK-23418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385907#comment-17385907
 ] 

Yang Wang commented on FLINK-23418:
---

The test failed because of timeout(30s) waiting for log "Restoring job 
 from Checkpoint". I did not find any 
exceptions, potential bugs for Kubernetes HA and recovery process. It just 
seems that the JobManager started and recover slowly. I will increase the 
timeout to 120s to make the {{test_kubernetes_application_ha.sh}} more stable.

> 'Run kubernetes application HA test' fail on Azure
> --
>
> Key: FLINK-23418
> URL: https://issues.apache.org/jira/browse/FLINK-23418
> Project: Flink
>  Issue Type: Bug
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.13.1
>Reporter: Dawid Wysakowicz
>Assignee: Yang Wang
>Priority: Major
>  Labels: test-stability
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20589=logs=68a897ab-3047-5660-245a-cce8f83859f6=16ca2cca-2f63-5cce-12d2-d519b930a729=3747
> {code}
> Jul 16 23:58:49   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:208)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:158)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.Actor$class.aroundReceive(Actor.scala:517) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.ActorCell.receiveMessage(ActorCell.scala:592) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.actor.ActorCell.invoke(ActorCell.scala:561) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.dispatch.Mailbox.run(Mailbox.scala:225) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.dispatch.Mailbox.exec(Mailbox.scala:235) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
>  [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49 Caused by: akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://flink@172.17.0.3:6123/user/rpc/jobmanager_2#2101744934]] 
> after [1 ms]. Message of type 
> [org.apache.flink.runtime.rpc.messages.RemoteFencedMessage]. A typical reason 
> for `AskTimeoutException` is that the recipient actor didn't send a reply.
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$2.apply(AskSupport.scala:635) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$2.apply(AskSupport.scala:635) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
>

[jira] [Updated] (FLINK-23418) 'Run kubernetes application HA test' fail on Azure



 [ 
https://issues.apache.org/jira/browse/FLINK-23418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang updated FLINK-23418:
--
Fix Version/s: 1.14.0

> 'Run kubernetes application HA test' fail on Azure
> --
>
> Key: FLINK-23418
> URL: https://issues.apache.org/jira/browse/FLINK-23418
> Project: Flink
>  Issue Type: Bug
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.13.1
>Reporter: Dawid Wysakowicz
>Priority: Major
>  Labels: test-stability
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20589=logs=68a897ab-3047-5660-245a-cce8f83859f6=16ca2cca-2f63-5cce-12d2-d519b930a729=3747
> {code}
> Jul 16 23:58:49   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:208)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:158)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.Actor$class.aroundReceive(Actor.scala:517) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.ActorCell.receiveMessage(ActorCell.scala:592) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.actor.ActorCell.invoke(ActorCell.scala:561) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.dispatch.Mailbox.run(Mailbox.scala:225) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.dispatch.Mailbox.exec(Mailbox.scala:235) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
>  [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49 Caused by: akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://flink@172.17.0.3:6123/user/rpc/jobmanager_2#2101744934]] 
> after [1 ms]. Message of type 
> [org.apache.flink.runtime.rpc.messages.RemoteFencedMessage]. A typical reason 
> for `AskTimeoutException` is that the recipient actor didn't send a reply.
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$2.apply(AskSupport.scala:635) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$2.apply(AskSupport.scala:635) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:648) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.Scheduler$$anon$4.run(Scheduler.scala:205) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49

[jira] [Assigned] (FLINK-23418) 'Run kubernetes application HA test' fail on Azure



 [ 
https://issues.apache.org/jira/browse/FLINK-23418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang reassigned FLINK-23418:
-

Assignee: Yang Wang

> 'Run kubernetes application HA test' fail on Azure
> --
>
> Key: FLINK-23418
> URL: https://issues.apache.org/jira/browse/FLINK-23418
> Project: Flink
>  Issue Type: Bug
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.13.1
>Reporter: Dawid Wysakowicz
>Assignee: Yang Wang
>Priority: Major
>  Labels: test-stability
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20589=logs=68a897ab-3047-5660-245a-cce8f83859f6=16ca2cca-2f63-5cce-12d2-d519b930a729=3747
> {code}
> Jul 16 23:58:49   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:208)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:158)
>  ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.Actor$class.aroundReceive(Actor.scala:517) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.ActorCell.receiveMessage(ActorCell.scala:592) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.actor.ActorCell.invoke(ActorCell.scala:561) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.dispatch.Mailbox.run(Mailbox.scala:225) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at akka.dispatch.Mailbox.exec(Mailbox.scala:235) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) 
> [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
>  [flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49 Caused by: akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://flink@172.17.0.3:6123/user/rpc/jobmanager_2#2101744934]] 
> after [1 ms]. Message of type 
> [org.apache.flink.runtime.rpc.messages.RemoteFencedMessage]. A typical reason 
> for `AskTimeoutException` is that the recipient actor didn't send a reply.
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$2.apply(AskSupport.scala:635) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$2.apply(AskSupport.scala:635) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:648) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> akka.actor.Scheduler$$anon$4.run(Scheduler.scala:205) 
> ~[flink-dist_2.11-1.13-SNAPSHOT.jar:1.13-SNAPSHOT]
> Jul 16 23:58:49   at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager



[ 
https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385892#comment-17385892
 ] 

Yang Wang commented on FLINK-22594:
---

I will try to find some time to have a look on the attached PR.

> Report oom killed pod in k8s resource manager
> -
>
> Key: FLINK-22594
> URL: https://issues.apache.org/jira/browse/FLINK-22594
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes
>Reporter: Aitozi
>Assignee: Aitozi
>Priority: Minor
>  Labels: pull-request-available
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (FLINK-22594) Report oom killed pod in k8s resource manager



 [ 
https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang reassigned FLINK-22594:
-

Assignee: Aitozi

> Report oom killed pod in k8s resource manager
> -
>
> Key: FLINK-22594
> URL: https://issues.apache.org/jira/browse/FLINK-22594
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes
>Reporter: Aitozi
>Assignee: Aitozi
>Priority: Minor
>  Labels: pull-request-available
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-23472) Math functions with DECIMAL argument should return DECIMAL result

2021-07-22 Thread Caizhi Weng (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Caizhi Weng updated FLINK-23472:

Component/s: Table SQL / API

> Math functions with DECIMAL argument should return DECIMAL result
> -
>
> Key: FLINK-23472
> URL: https://issues.apache.org/jira/browse/FLINK-23472
> Project: Flink
>  Issue Type: Bug
>  Components: Table SQL / API, Table SQL / Planner
>Reporter: Maciej Bryński
>Priority: Major
>
> Following functions will return DOUBLE type and should return DECIMAL instead
>  * LOG
>  * POWER
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-23472) Math functions with DECIMAL argument should return DECIMAL result

2021-07-22 Thread Caizhi Weng (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Caizhi Weng updated FLINK-23472:

Component/s: Table SQL / Planner

> Math functions with DECIMAL argument should return DECIMAL result
> -
>
> Key: FLINK-23472
> URL: https://issues.apache.org/jira/browse/FLINK-23472
> Project: Flink
>  Issue Type: Bug
>  Components: Table SQL / Planner
>Reporter: Maciej Bryński
>Priority: Major
>
> Following functions will return DOUBLE type and should return DECIMAL instead
>  * LOG
>  * POWER
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot edited a comment on pull request #16487: [FLINK-22483][runtime][coordination] Recover checkpoints when JobMaster gains leadership



flinkbot edited a comment on pull request #16487:
URL: https://github.com/apache/flink/pull/16487#issuecomment-879414939


   
   ## CI report:
   
   * 38d1e8ed584f6b780a0b1afd99abcdd9018b84f2 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20862)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] wuchong closed pull request #15821: [FLINK-21911][table] Add built-in greatest/least functions support



wuchong closed pull request #15821:
URL: https://github.com/apache/flink/pull/15821


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] wuchong commented on pull request #15821: [FLINK-21911][table] Add built-in greatest/least functions support



wuchong commented on pull request #15821:
URL: https://github.com/apache/flink/pull/15821#issuecomment-885359565


   Merged in #16020. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Closed] (FLINK-21911) Support GREATEST and LEAST functions in SQL

2021-07-22 Thread Jark Wu (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-21911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jark Wu closed FLINK-21911.
---
Fix Version/s: 1.14.0
 Assignee: Leonard Xu
   Resolution: Fixed

Fixed in master: cd7ca292b6c479aa7529bdc45813236fc0eaf3d0

> Support GREATEST and LEAST functions in SQL
> ---
>
> Key: FLINK-21911
> URL: https://issues.apache.org/jira/browse/FLINK-21911
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Timo Walther
>Assignee: Leonard Xu
>Priority: Major
>  Labels: auto-unassigned, pull-request-available
> Fix For: 1.14.0
>
>
> We should discuss if we want to support math MIN / MAX in Flink SQL. It seems 
> also other vendors do not support it out of the box:
> [https://stackoverflow.com/questions/124417/is-there-a-max-function-in-sql-server-that-takes-two-values-like-math-max-in-ne]
> But it might be quite useful and a common operation in JVM languages.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] wuchong commented on pull request #16020: [FLINK-21911][table-api] Add built-in greatest/least functions support #15821



wuchong commented on pull request #16020:
URL: https://github.com/apache/flink/pull/16020#issuecomment-885359458


   Thanks for the contribution @leonardBang  and the original contribution 
@snuyanzin


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] wuchong merged pull request #16020: [FLINK-21911][table-api] Add built-in greatest/least functions support #15821



wuchong merged pull request #16020:
URL: https://github.com/apache/flink/pull/16020


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (FLINK-23440) The "State. Backend" of "Flink-CONF.YAML" is inconsistent with the documentation

2021-07-22 Thread Yun Tang (Jira)



[ 
https://issues.apache.org/jira/browse/FLINK-23440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385876#comment-17385876
 ] 

Yun Tang commented on FLINK-23440:
--

[~yang89520] I have assigned this ticket to you, and you could check the 
{{org.apache.flink.runtime.state.StateBackendLoader.java}} to see the key word 
of different state backends. 

> The "State. Backend" of "Flink-CONF.YAML" is inconsistent with the 
> documentation
> 
>
> Key: FLINK-23440
> URL: https://issues.apache.org/jira/browse/FLINK-23440
> Project: Flink
>  Issue Type: Improvement
>  Components: Runtime / Configuration
>Affects Versions: 1.13.1
>Reporter: yang89520
>Assignee: yang89520
>Priority: Major
> Attachments: flink-conf.png, flink1_13_doc.png
>
>
> Flink1.13 document, describing "StateBackends" is "HashMapStateBackend" and 
> "EmbeddedRocksDBStateBackend". But the "flink-conf.yaml" configuration file 
> supports 'jobmanager', 'filesystem', 'rocksdb' and is not synchronized with 
> the document



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (FLINK-23440) The "State. Backend" of "Flink-CONF.YAML" is inconsistent with the documentation

2021-07-22 Thread Yun Tang (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yun Tang reassigned FLINK-23440:


Assignee: yang89520

> The "State. Backend" of "Flink-CONF.YAML" is inconsistent with the 
> documentation
> 
>
> Key: FLINK-23440
> URL: https://issues.apache.org/jira/browse/FLINK-23440
> Project: Flink
>  Issue Type: Improvement
>  Components: Runtime / Configuration
>Affects Versions: 1.13.1
>Reporter: yang89520
>Assignee: yang89520
>Priority: Major
> Attachments: flink-conf.png, flink1_13_doc.png
>
>
> Flink1.13 document, describing "StateBackends" is "HashMapStateBackend" and 
> "EmbeddedRocksDBStateBackend". But the "flink-conf.yaml" configuration file 
> supports 'jobmanager', 'filesystem', 'rocksdb' and is not synchronized with 
> the document



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-22054) Using a shared watcher for ConfigMap watching



 [ 
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang updated FLINK-22054:
--
Description: 
While using K8s HA service, the watching for ConfigMap is separate for each 
job. As the number of running jobs increases, this consumes a large amount of 
connections.

Here we proposal to use a shared watcher for each FlinkKubeClient, and dispatch 
events to different listeners. At the same time, we should keep the same 
semantic with watching separately.

  was:
While using K8s HA service, the watching for ConfigMap is separate for each 
job. As the number of running jobs increases, this consumes a large amount of 
connections.

Here we proposal to use a shard watcher for each FlinkKubeClient, and dispatch 
events to different listeners. At the same time, we should keep the same 
semantic with watching separately.


> Using a shared watcher for ConfigMap watching
> -
>
> Key: FLINK-22054
> URL: https://issues.apache.org/jira/browse/FLINK-22054
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.13.1, 1.12.4
>Reporter: Yi Tang
>Assignee: Yi Tang
>Priority: Major
>  Labels: k8s-ha, pull-request-available
> Fix For: 1.14.0
>
>
> While using K8s HA service, the watching for ConfigMap is separate for each 
> job. As the number of running jobs increases, this consumes a large amount of 
> connections.
> Here we proposal to use a shared watcher for each FlinkKubeClient, and 
> dispatch events to different listeners. At the same time, we should keep the 
> same semantic with watching separately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-22054) Using a shared watcher for ConfigMap watching



 [ 
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang updated FLINK-22054:
--
Affects Version/s: (was: 1.12.2)
   (was: 1.13.0)
   1.13.1
   1.12.4

> Using a shared watcher for ConfigMap watching
> -
>
> Key: FLINK-22054
> URL: https://issues.apache.org/jira/browse/FLINK-22054
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.13.1, 1.12.4
>Reporter: Yi Tang
>Assignee: Yi Tang
>Priority: Major
>  Labels: k8s-ha, pull-request-available
> Fix For: 1.14.0
>
>
> While using K8s HA service, the watching for ConfigMap is separate for each 
> job. As the number of running jobs increases, this consumes a large amount of 
> connections.
> Here we proposal to use a shard watcher for each FlinkKubeClient, and 
> dispatch events to different listeners. At the same time, we should keep the 
> same semantic with watching separately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] RollsBean edited a comment on pull request #16478: [FLINK-23228][docs-zh] Translate "Stateful Stream Processing" page into Chinese



RollsBean edited a comment on pull request #16478:
URL: https://github.com/apache/flink/pull/16478#issuecomment-885351001


   Hi @hackergin , thanks for your review and following up my PR, I made some 
changes as you suggested, aslo I reviewed my whole translation and did some 
updates.
   
   My updates as below(exclude you suggested):
   
   1. `有状态操作的一些示例：`  change to `一些有状态操作的示例：`
   2. `Keyed state 被维护在一个可以认为是键/值存储的地方。` change to `Keyed state 被维护在一个键/值存储的地方。`
   3. `在执行期间，每个有键算子的并行实例和一个或多个键组的键一起使用。` change to `在执行期间，每个 keyed operator 
的并行实例和一个或多个键组的键一起使用。`
   4. `例如在 Apache Kafka 中，这意味着告诉消费者（consumer）从 offset Sk 
开始获取。 ` change to `例如在 Apache Kafka 中，这意味着告诉消费者（consumer）从 offset 
Sk 开始获取。 `


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Closed] (FLINK-22054) Using a shared watcher for ConfigMap watching



 [ 
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang closed FLINK-22054.
-
Resolution: Fixed

> Using a shared watcher for ConfigMap watching
> -
>
> Key: FLINK-22054
> URL: https://issues.apache.org/jira/browse/FLINK-22054
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.12.2, 1.13.0
>Reporter: Yi Tang
>Assignee: Yi Tang
>Priority: Major
>  Labels: k8s-ha, pull-request-available
> Fix For: 1.14.0
>
>
> While using K8s HA service, the watching for ConfigMap is separate for each 
> job. As the number of running jobs increases, this consumes a large amount of 
> connections.
> Here we proposal to use a shard watcher for each FlinkKubeClient, and 
> dispatch events to different listeners. At the same time, we should keep the 
> same semantic with watching separately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-22054) Using a shared watcher for ConfigMap watching



 [ 
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yang Wang updated FLINK-22054:
--
Component/s: Deployment / Kubernetes

> Using a shared watcher for ConfigMap watching
> -
>
> Key: FLINK-22054
> URL: https://issues.apache.org/jira/browse/FLINK-22054
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Coordination
>Affects Versions: 1.12.2, 1.13.0
>Reporter: Yi Tang
>Assignee: Yi Tang
>Priority: Major
>  Labels: k8s-ha, pull-request-available
> Fix For: 1.14.0
>
>
> While using K8s HA service, the watching for ConfigMap is separate for each 
> job. As the number of running jobs increases, this consumes a large amount of 
> connections.
> Here we proposal to use a shard watcher for each FlinkKubeClient, and 
> dispatch events to different listeners. At the same time, we should keep the 
> same semantic with watching separately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot edited a comment on pull request #16559: [FLINK-18562] Support for Hadoop ABFS for Azure Datalake Gen2 accounts



flinkbot edited a comment on pull request #16559:
URL: https://github.com/apache/flink/pull/16559#issuecomment-884516771


   
   ## CI report:
   
   * 840b0ea0a6a6237c7a16a9f5adef4f7f7276791c Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20858)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] RollsBean commented on pull request #16478: [FLINK-23228][docs-zh] Translate "Stateful Stream Processing" page into Chinese



RollsBean commented on pull request #16478:
URL: https://github.com/apache/flink/pull/16478#issuecomment-885351001


   Hi @hackergin , thanks for your review and following up my PR, I make some 
changes as you suggested, aslo I review my whole translation and do some update.
   
   My update as below(exclude you suggested):
   
   1. `有状态操作的一些示例：`  change to `一些有状态操作的示例：`
   2. `Keyed state 被维护在一个可以认为是键/值存储的地方。` change to `Keyed state 被维护在一个键/值存储的地方。`
   3. `在执行期间，每个有键算子的并行实例和一个或多个键组的键一起使用。` change to `在执行期间，每个 keyed operator 
的并行实例和一个或多个键组的键一起使用。`
   4. `例如在 Apache Kafka 中，这意味着告诉消费者（consumer）从 offset Sk 
开始获取。 ` change to `例如在 Apache Kafka 中，这意味着告诉消费者（consumer）从 offset 
Sk 开始获取。 `


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16487: [FLINK-22483][runtime][coordination] Recover checkpoints when JobMaster gains leadership



flinkbot edited a comment on pull request #16487:
URL: https://github.com/apache/flink/pull/16487#issuecomment-879414939


   
   ## CI report:
   
   * ca29a17be6b7442c76f8160c56f0696655d7aba2 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20811)
 
   * 38d1e8ed584f6b780a0b1afd99abcdd9018b84f2 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (FLINK-22054) Using a shared watcher for ConfigMap watching



[ 
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385851#comment-17385851
 ] 

Yang Wang commented on FLINK-22054:
---

Merged in master via 

dfb4c003c84df6c4e3bf37dd506a0061fd3228f2

9c7e3007eea80d7f4ad602fc33d9f58b676a7722

 

> Using a shared watcher for ConfigMap watching
> -
>
> Key: FLINK-22054
> URL: https://issues.apache.org/jira/browse/FLINK-22054
> Project: Flink
>  Issue Type: Improvement
>  Components: Runtime / Coordination
>Affects Versions: 1.12.2, 1.13.0
>Reporter: Yi Tang
>Assignee: Yi Tang
>Priority: Major
>  Labels: k8s-ha, pull-request-available
> Fix For: 1.14.0
>
>
> While using K8s HA service, the watching for ConfigMap is separate for each 
> job. As the number of running jobs increases, this consumes a large amount of 
> connections.
> Here we proposal to use a shard watcher for each FlinkKubeClient, and 
> dispatch events to different listeners. At the same time, we should keep the 
> same semantic with watching separately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] wangyang0918 closed pull request #15501: [FLINK-22054][k8s] Using a shared watcher for ConfigMap watching



wangyang0918 closed pull request #15501:
URL: https://github.com/apache/flink/pull/15501


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] edu05 commented on pull request #16487: [FLINK-22483][runtime][coordination] Recover checkpoints when JobMaster gains leadership

edu05 commented on pull request #16487:
URL: https://github.com/apache/flink/pull/16487#issuecomment-885344162

Hi @dmvk while writing the acceptance test I found a couple of things that
don't quite make sense to me at the moment. Could you help please?

1. I have found the new call to the recover method to still be in the
JobMaster's main thread, not outside of it as desired. You can see this by
debugging the new IT I added to the PR with a breakpoint inside recover. I'm
attaching a sample image, notice how the call to recover is made from
SchedulerUtils (as intended) but that call is in turn made from inside
JobMaster's main thread, not outside.

![debug](https://user-images.githubusercontent.com/1392421/126728056-e14f36b4-bd74-4f9e-a4d6-807c98bf6b51.png)

2. Even if the call was made from a separate thread, the first call to
recover would only "warm up" for the period of time before the second call to
recover via CheckpointCoordinator. If the delay between both calls is shorter
than the time it takes for the first recover to execute, the JobMaster will
become stalled at that point and unable to take RPC calls.

Does that make sense?

--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] yittg commented on pull request #15501: [FLINK-22054][k8s] Using a shared watcher for ConfigMap watching



yittg commented on pull request #15501:
URL: https://github.com/apache/flink/pull/15501#issuecomment-885343922


   Thanks @wangyang0918 , @dmvk, and @tillrohrmann .
   Thanks for your help to make it happen. Glad to participate in improving 
Flink.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16575: [WIP][FLINK-23139][state] Add TaskStateRegistry



flinkbot edited a comment on pull request #16575:
URL: https://github.com/apache/flink/pull/16575#issuecomment-885295771


   
   ## CI report:
   
   * 74de0f3d61a1483e5e19cfc7d10369280c4cc82b Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20860)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot commented on pull request #16575: [WIP][FLINK-23139][state] Add TaskStateRegistry



flinkbot commented on pull request #16575:
URL: https://github.com/apache/flink/pull/16575#issuecomment-885295771


   
   ## CI report:
   
   * 74de0f3d61a1483e5e19cfc7d10369280c4cc82b UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot commented on pull request #16575: [WIP][FLINK-23139][state] Add TaskStateRegistry



flinkbot commented on pull request #16575:
URL: https://github.com/apache/flink/pull/16575#issuecomment-885282487


   Thanks a lot for your contribution to the Apache Flink project. I'm the 
@flinkbot. I help the community
   to review your pull request. We will use this comment to track the progress 
of the review.
   
   
   ## Automated Checks
   Last check on commit 62b832afafaf53d59ecc6585d920f129baa301cf (Thu Jul 22 
22:43:00 UTC 2021)
   
   **Warnings:**
* **64 pom.xml files were touched**: Check for build and licensing issues.
   
   
   Mention the bot in a comment to re-run the automated checks.
   ## Review Progress
   
   * ❓ 1. The [description] looks good.
   * ❓ 2. There is [consensus] that the contribution should go into to Flink.
   * ❓ 3. Needs [attention] from.
   * ❓ 4. The change fits into the overall [architecture].
   * ❓ 5. Overall code [quality] is good.
   
   Please see the [Pull Request Review 
Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full 
explanation of the review process.
The Bot is tracking the review progress through labels. Labels are applied 
according to the order of the review items. For consensus, approval by a Flink 
committer of PMC member is required Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot approve description` to approve one or more aspects (aspects: 
`description`, `consensus`, `architecture` and `quality`)
- `@flinkbot approve all` to approve all aspects
- `@flinkbot approve-until architecture` to approve everything until 
`architecture`
- `@flinkbot attention @username1 [@username2 ..]` to require somebody's 
attention
- `@flinkbot disapprove architecture` to remove an approval you gave earlier
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (FLINK-23437) Connection leak in XaFacadePoolingImpl

2021-07-22 Thread Roman Khachatryan (Jira)



[ 
https://issues.apache.org/jira/browse/FLINK-23437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385806#comment-17385806
 ] 

Roman Khachatryan commented on FLINK-23437:
---

Thanks [~maver1ck] for confirming  it.

I'll try to publish a PR this week (unless someone else would like to pick it).

> Connection leak in XaFacadePoolingImpl
> --
>
> Key: FLINK-23437
> URL: https://issues.apache.org/jira/browse/FLINK-23437
> Project: Flink
>  Issue Type: Bug
>  Components: Connectors / JDBC
>Affects Versions: 1.13.1
>Reporter: Maciej Bryński
>Priority: Major
>
> Hi,
> I'm using JDBC XA connector to put data into Oracle database.
> I'm facing issue with too many concurrent connection to database.
> I changed this method to return XaFacadeImpl instead of XaFacadePoolingImpl 
> and problem was solved.
> {code:java}
> static XaFacade fromXaDataSourceSupplier(
> Supplier dataSourceSupplier, Integer timeoutSec) {
> return new XaFacadePoolingImpl(() -> new XaFacadeImpl(dataSourceSupplier, 
> timeoutSec));
> }
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-23139) State ownership: track and discard private state (registry+changelog)

2021-07-22 Thread ASF GitHub Bot (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-23139:
---
Labels: pull-request-available  (was: )

> State ownership: track and discard private state (registry+changelog)
> -
>
> Key: FLINK-23139
> URL: https://issues.apache.org/jira/browse/FLINK-23139
> Project: Flink
>  Issue Type: Sub-task
>  Components: Runtime / State Backends
>Reporter: Roman Khachatryan
>Assignee: Roman Khachatryan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> TM should own changelog backend state to prevent re-uploading state on 
> checkpoint abortion (or missing confirmation). A simpler solution to only own 
> aborted state is less maintanable in the long run.
> For that, on TM state should be tracked and discarded (on 
> subsumption+materialization; on shutdown). 
> See [state ownership design 
> doc|https://docs.google.com/document/d/1NJJQ30P27BmUvD7oa4FChvkYxMEgjRPTVdO1dHLl_9I/edit?usp=sharing],
>  in particular [Tracking private 
> state|https://docs.google.com/document/d/1NJJQ30P27BmUvD7oa4FChvkYxMEgjRPTVdO1dHLl_9I/edit#heading=h.9dxopqajsy7].
>  
> This ticket is about creating TaskStateRegistry and using it in 
> ChangelogStateBackend (for non-materialized part only; for materialized see 
> FLINK-23344).
>   
> Externalized checkpoints and savepoints should be supported (or please create 
> a separate ticket).
>  
> Retained checkpoints is a separate ticket: FLINK-23251



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] rkhachatryan opened a new pull request #16575: [WIP][FLINK-23139][state] Add TaskStateRegistry



rkhachatryan opened a new pull request #16575:
URL: https://github.com/apache/flink/pull/16575


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (FLINK-22971) Initialization of Testcontainers unstable on Azure

2021-07-22 Thread Flink Jira Bot (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-22971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-22971:
---
  Labels: Umbrella auto-deprioritized-critical test-stability  (was: 
Umbrella stale-critical test-stability)
Priority: Major  (was: Critical)

This issue was labeled "stale-critical" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Critical, 
please raise the priority and ask a committer to assign you the issue or revive 
the public discussion.


> Initialization of Testcontainers unstable on Azure
> --
>
> Key: FLINK-22971
> URL: https://issues.apache.org/jira/browse/FLINK-22971
> Project: Flink
>  Issue Type: Bug
>  Components: Tests
>Reporter: Xintong Song
>Priority: Major
>  Labels: Umbrella, auto-deprioritized-critical, test-stability
>
> The following properties can be observed in many high-frequency test 
> instabilities. They are likely sharing a common root cause.
> * Use the Testcontainers framework
> * Fail due to no outputs in long time
> * A stack similar to the following can be find in the thread dump.
> ** Thread is RUNNABLE
> ** Testcontainers DockerClient is being created: 
> {{org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:205)}}
> ** Seems to be downloading something via okhttp
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7f4fec00b800 nid=0x4f56 runnable 
> [0x7f4ff536e000]
>java.lang.Thread.State: RUNNABLE
>   at org.testcontainers.shaded.okio.Buffer.getByte(Buffer.java:312)
>   at org.testcontainers.shaded.okio.Buffer.readUtf8Line(Buffer.java:766)
>   at 
> org.testcontainers.shaded.okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:231)
>   at 
> org.testcontainers.shaded.okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:224)
>   at 
> org.testcontainers.shaded.okhttp3.internal.http1.Http1ExchangeCodec$ChunkedSource.readChunkSize(Http1ExchangeCodec.java:489)
>   at 
> org.testcontainers.shaded.okhttp3.internal.http1.Http1ExchangeCodec$ChunkedSource.read(Http1ExchangeCodec.java:471)
>   at 
> org.testcontainers.shaded.okhttp3.internal.Util.skipAll(Util.java:204)
>   at 
> org.testcontainers.shaded.okhttp3.internal.Util.discard(Util.java:186)
>   at 
> org.testcontainers.shaded.okhttp3.internal.http1.Http1ExchangeCodec$ChunkedSource.close(Http1ExchangeCodec.java:511)
>   at 
> org.testcontainers.shaded.okio.ForwardingSource.close(ForwardingSource.java:43)
>   at 
> org.testcontainers.shaded.okhttp3.internal.connection.Exchange$ResponseBodySource.close(Exchange.java:313)
>   at 
> org.testcontainers.shaded.okio.RealBufferedSource.close(RealBufferedSource.java:476)
>   at 
> org.testcontainers.shaded.okhttp3.internal.Util.closeQuietly(Util.java:139)
>   at 
> org.testcontainers.shaded.okhttp3.ResponseBody.close(ResponseBody.java:192)
>   at org.testcontainers.shaded.okhttp3.Response.close(Response.java:290)
>   at 
> org.testcontainers.shaded.com.github.dockerjava.okhttp.OkDockerHttpClient$OkResponse.close(OkDockerHttpClient.java:285)
>   at 
> org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$null$0(DefaultInvocationBuilder.java:272)
>   at 
> org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder$$Lambda$96/1409690119.close(Unknown
>  Source)
>   at 
> com.github.dockerjava.api.async.ResultCallbackTemplate.close(ResultCallbackTemplate.java:77)
>   at 
> org.testcontainers.utility.ResourceReaper.start(ResourceReaper.java:202)
>   at 
> org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:205)
>   - locked <0x8980f398> (a [Ljava.lang.Object;)
>   at 
> org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
>   at 
> org.testcontainers.LazyDockerClient.listImagesCmd(LazyDockerClient.java:12)
>   at 
> org.testcontainers.images.LocalImagesCache.maybeInitCache(LocalImagesCache.java:68)
>   - locked <0x8980f3e8> (a 
> org.testcontainers.images.LocalImagesCache)
>   at 
> org.testcontainers.images.LocalImagesCache.get(LocalImagesCache.java:32)
>   at 
> org.testcontainers.images.AbstractImagePullPolicy.shouldPull(AbstractImagePullPolicy.java:18)
>   at 
> org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:66)
>   at 
> org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:27)
>   at 
> org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:17)
>   - locked <0x8980f478> (a 
> java.util.concurrent.atomic.AtomicReference)
>   at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:39)
>   at 
>

[jira] [Updated] (FLINK-23043) Wrong master address displayed when run application in native K8s with -Dkubernetes.rest-service.exposed.type=NodePort

2021-07-22 Thread Flink Jira Bot (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-23043:
---
Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> Wrong master address displayed when run application in native K8s with 
> -Dkubernetes.rest-service.exposed.type=NodePort
> --
>
> Key: FLINK-23043
> URL: https://issues.apache.org/jira/browse/FLINK-23043
> Project: Flink
>  Issue Type: Bug
>  Components: Deployment / Kubernetes
>Affects Versions: 1.13.1
>Reporter: Shang Yuanchun
>Assignee: Shang Yuanchun
>Priority: Major
>  Labels: pull-request-available, stale-assigned
> Fix For: 1.14.0
>
>
> When running with Native Kubernetes in application mode, and Fabric8 
> Kubernetes client is configured by Service account, if you specify 
> -Dkubernetes.rest-service.exposed.type=NodePort, the IP address in JobManager 
> Web Interface url displayed is not master node, but instead it is the 
> ClusterIP of service kubernetes.default.svc.
> Steps to reproduce:
> 1.Start a Kubernetes cluster
>  2.Bind ClusterRole edit to service account: default (for simplicity here)
> 3.Run kubectl run flink --image flink:latest sleep inf
> 4.Into container of step 3, run 
> ./bin/flink run-application --target kubernetes-application 
> -Dkubernetes.cluster-id=my-application-cluster 
> -Dkubernetes.container.image=flink:latest 
> -Dkubernetes.rest-service.exposed.type=NodePort 
> local:///opt/flink/examples/streaming/TopSpeedWindowing.jar
> Here it will say that JobManager Web interface is at [http://10.96.0.1:32333 
> |http://10.96.0.1:32368/]
> But actually 10.96.0.1 here is the environment variable of 
> KUBERNETES_SERVICE_HOST, and it is the ClusterIP of service 
> kubernetes.default.svc, not the address of master node, so 
> [http://10.96.0.1:32333|http://10.96.0.1:32368/] is not accessiable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] rkhachatryan commented on a change in pull request #16447: [FLINK-23144][metrics] Add percentiles to checkpoint statistics



rkhachatryan commented on a change in pull request #16447:
URL: https://github.com/apache/flink/pull/16447#discussion_r675205217



##
File path: 
flink-runtime-web/web-dashboard/src/app/pages/job/checkpoints/job-checkpoints.component.html
##
@@ -193,15 +193,74 @@
 {{ checkPointStats['summary']['state_size']['avg'] | 
humanizeBytes }}
 {{ checkPointStats['summary']['processed_data']['avg'] | 
humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['avg'] | 
humanizeBytes }})
   
-  
-Maximum
-{{ checkPointStats['summary']['end_to_end_duration']['max'] | 
humanizeDuration}}
-{{ checkPointStats['summary']['state_size']['max'] | 
humanizeBytes }}
-{{ checkPointStats['summary']['processed_data']['max'] | 
humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['max'] | 
humanizeBytes }})
-  
+
+Maximum
+{{ 
checkPointStats['summary']['end_to_end_duration']['max'] | 
humanizeDuration}}
+{{ checkPointStats['summary']['state_size']['max'] | 
humanizeBytes }}
+{{ checkPointStats['summary']['processed_data']['max'] | 
humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['max'] | 
humanizeBytes }})
+
 
   
 
+
+
+
+
+
+
+
+End to End Duration
+Checkpointed Data Size
+Processed (persisted) in-flight 
data
+
+
+
+
+
+50% percentile
+{{ 
checkPointStats['summary']['end_to_end_duration']['p50'] | 
humanizeDuration}}
+{{ checkPointStats['summary']['state_size']['p50'] | 
humanizeBytes }}
+{{ checkPointStats['summary']['processed_data']['p50'] 
| humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['p50'] | 
humanizeBytes }})
+
+
+90% percentile
+{{ 
checkPointStats['summary']['end_to_end_duration']['p90'] | 
humanizeDuration}}
+{{ checkPointStats['summary']['state_size']['p90'] | 
humanizeBytes }}
+{{ checkPointStats['summary']['processed_data']['p90'] 
| humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['p90'] | 
humanizeBytes }})
+
+
+99% percentile
+{{ 
checkPointStats['summary']['end_to_end_duration']['p99'] | 
humanizeDuration}}
+{{ checkPointStats['summary']['state_size']['p99'] | 
humanizeBytes }}
+{{ checkPointStats['summary']['processed_data']['p99'] 
| humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['p99'] | 
humanizeBytes }})
+
+
+99% percentile
+{{ 
checkPointStats['summary']['end_to_end_duration']['p99'] | 
humanizeDuration}}
+{{ checkPointStats['summary']['state_size']['p99'] | 
humanizeBytes }}
+{{ checkPointStats['summary']['processed_data']['p99'] 
| humanizeBytes }} ({{ checkPointStats['summary']['persisted_data']['p99'] | 
humanizeBytes }})
+
+
+99.9% percentile

Review comment:
   20.8 days doesn't sound like a very long period to me:)
   
   And for the ChangelogBackend, the target interval can be around 1s, so we'd 
need around 3hrs, which sounds reasonable even for tests.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16574: [FLINK-23467][e2e] Remove usage of the YAML file in pyflink.sh



flinkbot edited a comment on pull request #16574:
URL: https://github.com/apache/flink/pull/16574#issuecomment-884942041


   
   ## CI report:
   
   * c136ba59d056c623a3277418d015e170194a6826 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20854)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16368: ignore



flinkbot edited a comment on pull request #16368:
URL: https://github.com/apache/flink/pull/16368#issuecomment-873854539


   
   ## CI report:
   
   * 7cbf431d22c690f634babe740158b1129fa689c5 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20853)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Closed] (FLINK-23476) Snapshot deployments are broken

2021-07-22 Thread Chesnay Schepler (Jira)



 [ 
https://issues.apache.org/jira/browse/FLINK-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chesnay Schepler closed FLINK-23476.

Resolution: Fixed

master: b19a515ec3ec593c4e1c05c0dbf5c971e104fdf4 

> Snapshot deployments are broken
> ---
>
> Key: FLINK-23476
> URL: https://issues.apache.org/jira/browse/FLINK-23476
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / Azure Pipelines
>Affects Versions: 1.14.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Major
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=eca6b3a6-1600-56cc-916a-c549b3cde3ff=e9844b5e-5aa3-546b-6c3e-5395c7c0cac7
> {code}
> [ERROR] 'dependencies.dependency.version' for 
> com.typesafe.akka:akka-testkit_2.11:jar must be a valid version but is 
> '${akka.version}'. @ line 1212, column 15
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot edited a comment on pull request #16559: [FLINK-18562] Support for Hadoop ABFS for Azure Datalake Gen2 accounts



flinkbot edited a comment on pull request #16559:
URL: https://github.com/apache/flink/pull/16559#issuecomment-884516771


   
   ## CI report:
   
   * 7b469bc680f4b104a3673b2d146d706a602e12f9 Azure: 
[CANCELED](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20806)
 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20807)
 
   * 840b0ea0a6a6237c7a16a9f5adef4f7f7276791c Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20858)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (FLINK-23476) Snapshot deployments are broken

2021-07-22 Thread Chesnay Schepler (Jira)

Chesnay Schepler created FLINK-23476:


 Summary: Snapshot deployments are broken
 Key: FLINK-23476
 URL: https://issues.apache.org/jira/browse/FLINK-23476
 Project: Flink
  Issue Type: Bug
  Components: Build System / Azure Pipelines
Affects Versions: 1.14.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.14.0


https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20855=logs=eca6b3a6-1600-56cc-916a-c549b3cde3ff=e9844b5e-5aa3-546b-6c3e-5395c7c0cac7
{code}
[ERROR] 'dependencies.dependency.version' for 
com.typesafe.akka:akka-testkit_2.11:jar must be a valid version but is 
'${akka.version}'. @ line 1212, column 15
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] flinkbot edited a comment on pull request #16559: [FLINK-18562] Support for Hadoop ABFS for Azure Datalake Gen2 accounts



flinkbot edited a comment on pull request #16559:
URL: https://github.com/apache/flink/pull/16559#issuecomment-884516771


   
   ## CI report:
   
   * 7b469bc680f4b104a3673b2d146d706a602e12f9 Azure: 
[CANCELED](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20806)
 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20807)
 
   * 840b0ea0a6a6237c7a16a9f5adef4f7f7276791c UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #15501: [FLINK-22054][k8s] Using a shared watcher for ConfigMap watching



flinkbot edited a comment on pull request #15501:
URL: https://github.com/apache/flink/pull/15501#issuecomment-814722337


   
   ## CI report:
   
   * 4d82d3eea5137b32bd38dbaa3340af62906e3cd5 UNKNOWN
   * 65fc2e6abd18a5b5087e1e318a491202ded69940 UNKNOWN
   * ebec5a2750a5fd510b80ae80e7a9869133f7ce67 UNKNOWN
   * 1e9f33b6c69286b8c9748f828229641b84ed76e0 UNKNOWN
   * f7a474f088cb0cf62e7ef46d95289dded6139ee2 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20847)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16574: [FLINK-23467][e2e] Remove usage of the YAML file in pyflink.sh



flinkbot edited a comment on pull request #16574:
URL: https://github.com/apache/flink/pull/16574#issuecomment-884942041


   
   ## CI report:
   
   * 31adb55968e4e5c1749ba7de13f64ebaf8433914 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20846)
 
   * c136ba59d056c623a3277418d015e170194a6826 Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20854)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16368: ignore



flinkbot edited a comment on pull request #16368:
URL: https://github.com/apache/flink/pull/16368#issuecomment-873854539


   
   ## CI report:
   
   * 909a6a116db1fd65e8a8332f5d0e095e42df342f Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20795)
 
   * 7cbf431d22c690f634babe740158b1129fa689c5 Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20853)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16574: [FLINK-23467][e2e] Remove usage of the YAML file in pyflink.sh



flinkbot edited a comment on pull request #16574:
URL: https://github.com/apache/flink/pull/16574#issuecomment-884942041


   
   ## CI report:
   
   * 31adb55968e4e5c1749ba7de13f64ebaf8433914 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20846)
 
   * c136ba59d056c623a3277418d015e170194a6826 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16368: ignore



flinkbot edited a comment on pull request #16368:
URL: https://github.com/apache/flink/pull/16368#issuecomment-873854539


   
   ## CI report:
   
   * 909a6a116db1fd65e8a8332f5d0e095e42df342f Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20795)
 
   * 7cbf431d22c690f634babe740158b1129fa689c5 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16478: [FLINK-23228][docs-zh] Translate "Stateful Stream Processing" page into Chinese



flinkbot edited a comment on pull request #16478:
URL: https://github.com/apache/flink/pull/16478#issuecomment-878958342


   
   ## CI report:
   
   * dd0ac23c04fec173bfb90bf2ad500d15899b UNKNOWN
   * fead4ced5fd7e5b40f9dad198ad3d3ca088510f0 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20848)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (FLINK-18574) DownloadPipelineArtifact failed occasionally



[ 
https://issues.apache.org/jira/browse/FLINK-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385687#comment-17385687
 ] 

Dawid Wysakowicz commented on FLINK-18574:
--

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20828=logs=c5f0071e-1851-543e-9a45-9ac140befc32=b97d99b0-29a0-5024-77e6-a62d129b5139=1

> DownloadPipelineArtifact failed occasionally
> 
>
> Key: FLINK-18574
> URL: https://issues.apache.org/jira/browse/FLINK-18574
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / Azure Pipelines
>Reporter: Dian Fu
>Priority: Critical
>  Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=4414=logs=bdd9ea51-4de2-506a-d4d9-f3930e4d2355=c1dcc74d-b153-580b-95a4-73d5cd91b503
> {code}
> 2020-07-11T20:38:15.9784577Z ##[section]Starting: DownloadPipelineArtifact
> 2020-07-11T20:38:15.9799212Z 
> ==
> 2020-07-11T20:38:15.9799811Z Task : Download Pipeline Artifacts
> 2020-07-11T20:38:15.9800305Z Description  : Download build and pipeline 
> artifacts
> 2020-07-11T20:38:15.9800753Z Version  : 2.3.1
> 2020-07-11T20:38:15.9801328Z Author   : Microsoft Corporation
> 2020-07-11T20:38:15.9801942Z Help : 
> https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/download-pipeline-artifact
> 2020-07-11T20:38:15.9802614Z 
> ==
> 2020-07-11T20:38:16.5226960Z Download from the specified build: #4414
> 2020-07-11T20:38:16.5246147Z Download artifact to: 
> /home/agent07/myagent/_work/2/flink_artifact
> 2020-07-11T20:38:20.6397951Z Information, ApplicationInsightsTelemetrySender 
> will correlate events with X-TFS-Session 38415228-535b-4652-8afc-41e3fcfa5c67
> 2020-07-11T20:38:20.6546003Z Information, DedupManifestArtifactClient will 
> correlate http requests with X-TFS-Session 
> 38415228-535b-4652-8afc-41e3fcfa5c67
> 2020-07-11T20:38:20.6563787Z Information, Minimatch patterns: [**]
> 2020-07-11T20:38:20.7577072Z Information, 
> ArtifactHttpRetryMessageHandler.SendAsync: 
> https://vsblobprodsu6weu.vsblob.visualstudio.com/A2d3c0ac8-fecf-45be-8407-6d87302181a9/_apis/dedup/nodes/4C7343B40F7AB12049F6929A6A4ECD738EFADAC85D010AF5877ACD0682CC6C5802
>  attempt 1/6 failed with StatusCode RedirectMethod, IsRetryableResponse False
> 2020-07-11T20:38:35.8527079Z Information, Filtered 130283 files from the 
> Minimatch filters supplied.
> 2020-07-11T20:38:35.8865820Z Information, Downloaded 0.0 MB out of 1,170.3 MB 
> (0%).
> 2020-07-11T20:38:40.8869716Z Information, Downloaded 4.6 MB out of 1,170.3 MB 
> (0%).
> 2020-07-11T20:38:45.9379430Z Information, Downloaded 24.5 MB out of 1,170.3 
> MB (2%).
> 2020-07-11T20:38:50.9539945Z Information, Downloaded 41.8 MB out of 1,170.3 
> MB (4%).
> 2020-07-11T20:38:53.5482129Z Warning, 
> [https://nsevsblobprodsu6weus42.blob.core.windows.net/db2d3c0ac8fecf45be84076d87302181a9/454487F48A36900D2D7FE8928376FDB49F9F3BF90B3A5474B7EF8D9ABE8BDC7201?sv=2019-02-02=b=HGudFZh7Cd3TOBUMGO7rIq0DJxPQORzHkSVs3iYeDPc%3D=https=2020-07-12T21%3A16%3A18Z=r=x-e2eid-e61f9696-89054b42-93868ec3-c0739ba7-session-38415228-535b4652-8afc41e3-fcfa5c67]
>  Try 1/5, retryable exception caught. Retrying in 00:00:01. 
> System.Net.Http.HttpRequestException: An error occurred while sending the 
> request.
> 2020-07-11T20:38:53.5484031Z  ---> System.Net.Http.CurlException: Couldn't 
> connect to server
> 2020-07-11T20:38:53.5484420Zat 
> System.Net.Http.CurlHandler.ThrowIfCURLEError(CURLcode error)
> 2020-07-11T20:38:53.5484929Zat 
> System.Net.Http.CurlHandler.MultiAgent.FinishRequest(StrongToWeakReference`1 
> easyWrapper, CURLcode messageResult)
> 2020-07-11T20:38:53.5485733Z--- End of inner exception stack trace ---
> 2020-07-11T20:38:53.5486394Zat 
> System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, 
> HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
> 2020-07-11T20:38:53.5487612Zat 
> Microsoft.VisualStudio.Services.Common.TaskCancellationExtensions.EnforceCancellation[TResult](Task`1
>  task, CancellationToken cancellationToken, Func`1 makeMessage, String file, 
> String member, Int32 line)
> 2020-07-11T20:38:53.5488656Zat 
> Microsoft.VisualStudio.Services.BlobStore.WebApi.DedupStoreHttpClient.<>c__DisplayClass57_0.d.MoveNext()
> 2020-07-11T20:38:53.5489700Z --- End of stack trace from previous location 
> where exception was thrown ---
> 2020-07-11T20:38:53.5490174Zat 
> Microsoft.VisualStudio.Services.Content.Common.AsyncHttpRetryHelper`1.InvokeAsync(CancellationToken
>  cancellationToken)
> 2020-07-11T20:38:53.5539270Z Warning, 
>

[jira] [Commented] (FLINK-21411) The components on which Flink depends may contain vulnerabilities. If yes, fix them.

2021-07-22 Thread Till Rohrmann (Jira)



[ 
https://issues.apache.org/jira/browse/FLINK-21411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385680#comment-17385680
 ] 

Till Rohrmann commented on FLINK-21411:
---

Fixed the FRocksDB vulnerability via

master: 26aa7b459e0ff1a83a49b1602144e668b3a6a6ce
1.13.2: f5bce736ac6138f9b9fd7d36f63578a54e28b23e
1.12.5: 7cbf431d22c690f634babe740158b1129fa689c5
1.11.4: b1177cd0170d60310f6b57e4f3edd850a5e9dda2


> The components on which Flink depends may contain vulnerabilities. If yes, 
> fix them.
> 
>
> Key: FLINK-21411
> URL: https://issues.apache.org/jira/browse/FLINK-21411
> Project: Flink
>  Issue Type: Improvement
>  Components: Build System
>Reporter: dgbro
>Priority: Minor
>  Labels: auto-deprioritized-major, pull-request-available
>
> In Flink v1.11.3 contains mesos(version: 1.0.1) okhttp(version: 3.7.0) 
> log4j(version:2.12.1) netty(version:3.10.6) jackson-databind(2.10.1) 
> jackson(version:2.10.1) and bzip2(version:1.0.6). There are many 
> vulnerabilities, like 
> CVE-2017-7687,CVE-2017-9790,CVE-2018-8023,CVE-2018-20200,CVE-2020-9488,CVE-2019-20444,CVE-2019-20445,CVE-2019-16869,CVE-2020-25649,CVE-2020-25649,CVE-2019-12900,CVE-2016-3189,CVE-2018-8088
>  etc. please confirm these version and fix. thx



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [flink] tillrohrmann merged pull request #16572: [FLINK-21411][rocksdb] Update FRocksDB to bump bzip2 dependency version



tillrohrmann merged pull request #16572:
URL: https://github.com/apache/flink/pull/16572


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] tillrohrmann commented on pull request #16572: [FLINK-21411][rocksdb] Update FRocksDB to bump bzip2 dependency version



tillrohrmann commented on pull request #16572:
URL: https://github.com/apache/flink/pull/16572#issuecomment-885084134


   The failed e2e test looks unrelated.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] tillrohrmann merged pull request #16573: [FLINK-21411][rocksdb] Update FRocksDB to bump bzip2 dependency version



tillrohrmann merged pull request #16573:
URL: https://github.com/apache/flink/pull/16573


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] tillrohrmann merged pull request #16569: [FLINK-21411][rocksdb] Update FRocksDB to bump bzip2 dependency version



tillrohrmann merged pull request #16569:
URL: https://github.com/apache/flink/pull/16569


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] tillrohrmann closed pull request #16568: [FLINK-21411][rocksdb] Update FRocksDB to bump bzip2 dependency version



tillrohrmann closed pull request #16568:
URL: https://github.com/apache/flink/pull/16568


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16478: [FLINK-23228][docs-zh] Translate "Stateful Stream Processing" page into Chinese



flinkbot edited a comment on pull request #16478:
URL: https://github.com/apache/flink/pull/16478#issuecomment-878958342


   
   ## CI report:
   
   * dd0ac23c04fec173bfb90bf2ad500d15899b UNKNOWN
   * 2e89f05d259f1d5ddf382a05e2f9e142aa58d9e4 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20744)
 
   * fead4ced5fd7e5b40f9dad198ad3d3ca088510f0 Azure: 
[PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20848)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] yiduwangkai commented on pull request #16532: [FLINK-13400]Remove Hive and Hadoop dependencies from SQL Client



yiduwangkai commented on pull request #16532:
URL: https://github.com/apache/flink/pull/16532#issuecomment-885061918


   @lirui-apache how do you think about this


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] yiduwangkai commented on pull request #16532: [FLINK-13400]Remove Hive and Hadoop dependencies from SQL Client



yiduwangkai commented on pull request #16532:
URL: https://github.com/apache/flink/pull/16532#issuecomment-885060211


   @fsk119 hi, according to you,the amount of work will be a bit huge，First of 
all, I need to run a hive docker environment. I see the code, and I seem to 
need to modify the docker file, because I need to create the hive image by 
myself, right?，and then I need to run the sql-client.sh script to perform e2e 
testing，right?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16571: [hotfix][connector/kafka] fix missing nullable annotion



flinkbot edited a comment on pull request #16571:
URL: https://github.com/apache/flink/pull/16571#issuecomment-884882802


   
   ## CI report:
   
   * 18b95daab0297d86041683e92112c75b17c17bc8 Azure: 
[FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20843)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16573: [FLINK-21411][rocksdb] Update FRocksDB to bump bzip2 dependency version



flinkbot edited a comment on pull request #16573:
URL: https://github.com/apache/flink/pull/16573#issuecomment-884883091


   
   ## CI report:
   
   * 65854e2e7879deb6e29690dd0b13fcd42b795754 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20845)
 
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #16478: [FLINK-23228][docs-zh] Translate "Stateful Stream Processing" page into Chinese



flinkbot edited a comment on pull request #16478:
URL: https://github.com/apache/flink/pull/16478#issuecomment-878958342


   
   ## CI report:
   
   * dd0ac23c04fec173bfb90bf2ad500d15899b UNKNOWN
   * 2e89f05d259f1d5ddf382a05e2f9e142aa58d9e4 Azure: 
[SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=20744)
 
   * fead4ced5fd7e5b40f9dad198ad3d3ca088510f0 UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [flink] flinkbot edited a comment on pull request #15501: [FLINK-22054][k8s] Using a shared watcher for ConfigMap watching