[jira] [Commented] (FLINK-32833) Rocksdb CacheIndexAndFilterBlocks must be true when using shared memory
[
https://issues.apache.org/jira/browse/FLINK-32833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753650#comment-17753650
]
Yue Ma commented on FLINK-32833:
hi [~yunta] thank you for your replying.
I understand the original purpose of these codes. These configurations can help
we limit memory usage better.
What I want to say is that the user may need to decide to configure these
parameters instead of hardcoding them in the flink code. In our previous tests,
we found that indexAndFiltlers has a great impact on performance, especially in
hdd environment. In the current flink version, if the user uses shared memory
at the same time and wants to ensure high performance, it may also need to set
an appropriate WRITE_BUFFER_RATIO or HIGH_PRIORITY_POOL_RATIO , which may be
difficult for the user mode. In other words, if the user only wants to put the
datablock in the cache, and wants the meta information of indexAndFilter to be
resident in memory, it also sounds reasonable. What do you think ?
> Rocksdb CacheIndexAndFilterBlocks must be true when using shared memory
> ---
>
> Key: FLINK-32833
> URL: https://issues.apache.org/jira/browse/FLINK-32833
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Affects Versions: 1.17.1
>Reporter: Yue Ma
>Priority: Major
>
> Currently in RocksDBResourceContainer#getColumnOptions, if sharedResources is
> used, blockBasedTableConfig will add the following configuration by default.
> {code:java}
> blockBasedTableConfig.setBlockCache(blockCache);
> blockBasedTableConfig.setCacheIndexAndFilterBlocks(true);
> blockBasedTableConfig.setCacheIndexAndFilterBlocksWithHighPriority(true);
> blockBasedTableConfig.setPinL0FilterAndIndexBlocksInCache(true);{code}
> In my understanding, these configurations can help flink better manage the
> memory of rocksdb and save some memory overhead in some scenarios. But this
> may not be the best practice, mainly for the following reasons:
> 1. After CacheIndexAndFilterBlocks is set to true, it may cause index and
> filter miss when reading, resulting in performance degradation.
> 2. These parameters may not be bound together with whether shared memory is
> used, or some configurations should be supported separately to decide whether
> to enable these features
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FLINK-32820) ParameterTool is mistakenly marked as deprecated
[ https://issues.apache.org/jira/browse/FLINK-32820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song closed FLINK-32820. Fix Version/s: 1.18.0 Resolution: Fixed master (1.18): fc2b5d8f53a41695117f6eaf4c798cc183cf1e36 > ParameterTool is mistakenly marked as deprecated > > > Key: FLINK-32820 > URL: https://issues.apache.org/jira/browse/FLINK-32820 > Project: Flink > Issue Type: Bug > Components: API / DataSet, API / DataStream >Affects Versions: 1.18.0 >Reporter: Zhanghao Chen >Assignee: Zhanghao Chen >Priority: Major > Labels: pull-request-available > Fix For: 1.18.0 > > > ParameterTool and AbstractParameterTool in pacakge flink-java is mistakenly > marked as deprecated in [FLINK-32558] Properly deprecate DataSet API - ASF > JIRA (apache.org). They are widely used for handling application parameters > and is also listed in the Flink user doc: > [https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/application_parameters/.|https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/application_parameters/] > Also, they are not directly related to Dataset API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-31689) Filesystem sink fails when parallelism of compactor operator changed
[
https://issues.apache.org/jira/browse/FLINK-31689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753648#comment-17753648
]
jirawech.s commented on FLINK-31689:
waiting for PR review https://github.com/apache/flink/pull/22400
> Filesystem sink fails when parallelism of compactor operator changed
>
>
> Key: FLINK-31689
> URL: https://issues.apache.org/jira/browse/FLINK-31689
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem
>Affects Versions: 1.16.1
>Reporter: jirawech.s
>Assignee: jirawech.s
>Priority: Major
> Labels: pull-request-available
> Attachments: HelloFlinkHadoopSink.java
>
>
> I encounter this error when i tried to use Filesystem sink with Table SQL. I
> have not tested with Datastream API tho. You may refers to the error as below
> {code:java}
> // code placeholder
> java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:864)
> at
> org.apache.flink.connector.file.table.stream.compact.CompactOperator.initializeState(CompactOperator.java:119)
> at
> org.apache.flink.streaming.api.operators.StreamOperatorStateHandler.initializeOperatorState(StreamOperatorStateHandler.java:122)
> at
> org.apache.flink.streaming.api.operators.AbstractStreamOperator.initializeState(AbstractStreamOperator.java:286)
> at
> org.apache.flink.streaming.runtime.tasks.RegularOperatorChain.initializeStateAndOpenOperators(RegularOperatorChain.java:106)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.restoreGates(StreamTask.java:700)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTaskActionExecutor$1.call(StreamTaskActionExecutor.java:55)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.restoreInternal(StreamTask.java:676)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.restore(StreamTask.java:643)
> at
> org.apache.flink.runtime.taskmanager.Task.runWithSystemExitMonitoring(Task.java:948)
> at
> org.apache.flink.runtime.taskmanager.Task.restoreAndInvoke(Task.java:917)
> at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:741)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:563)
> at java.lang.Thread.run(Thread.java:750) {code}
> I cannot attach the full reproducible code here, but you may follow my pseudo
> code in attachment and reproducible steps below
> 1. Create Kafka source
> 2. Set state.savepoints.dir
> 3. Set Job parallelism to 1
> 4. Create FileSystem Sink
> 5. Run the job and trigger savepoint with API
> {noformat}
> curl -X POST localhost:8081/jobs/:jobId/savepoints -d '{"cancel-job":
> false}'{noformat}
> {color:#172b4d}6. Cancel job, change parallelism to 2, and resume job from
> savepoint{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31689) Filesystem sink fails when parallelism of compactor operator changed
[
https://issues.apache.org/jira/browse/FLINK-31689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jirawech.s updated FLINK-31689:
---
Labels: pull-request-available (was: pull-request-available stale-assigned)
> Filesystem sink fails when parallelism of compactor operator changed
>
>
> Key: FLINK-31689
> URL: https://issues.apache.org/jira/browse/FLINK-31689
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem
>Affects Versions: 1.16.1
>Reporter: jirawech.s
>Assignee: jirawech.s
>Priority: Major
> Labels: pull-request-available
> Attachments: HelloFlinkHadoopSink.java
>
>
> I encounter this error when i tried to use Filesystem sink with Table SQL. I
> have not tested with Datastream API tho. You may refers to the error as below
> {code:java}
> // code placeholder
> java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:864)
> at
> org.apache.flink.connector.file.table.stream.compact.CompactOperator.initializeState(CompactOperator.java:119)
> at
> org.apache.flink.streaming.api.operators.StreamOperatorStateHandler.initializeOperatorState(StreamOperatorStateHandler.java:122)
> at
> org.apache.flink.streaming.api.operators.AbstractStreamOperator.initializeState(AbstractStreamOperator.java:286)
> at
> org.apache.flink.streaming.runtime.tasks.RegularOperatorChain.initializeStateAndOpenOperators(RegularOperatorChain.java:106)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.restoreGates(StreamTask.java:700)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTaskActionExecutor$1.call(StreamTaskActionExecutor.java:55)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.restoreInternal(StreamTask.java:676)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.restore(StreamTask.java:643)
> at
> org.apache.flink.runtime.taskmanager.Task.runWithSystemExitMonitoring(Task.java:948)
> at
> org.apache.flink.runtime.taskmanager.Task.restoreAndInvoke(Task.java:917)
> at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:741)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:563)
> at java.lang.Thread.run(Thread.java:750) {code}
> I cannot attach the full reproducible code here, but you may follow my pseudo
> code in attachment and reproducible steps below
> 1. Create Kafka source
> 2. Set state.savepoints.dir
> 3. Set Job parallelism to 1
> 4. Create FileSystem Sink
> 5. Run the job and trigger savepoint with API
> {noformat}
> curl -X POST localhost:8081/jobs/:jobId/savepoints -d '{"cancel-job":
> false}'{noformat}
> {color:#172b4d}6. Cancel job, change parallelism to 2, and resume job from
> savepoint{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [flink] xintongsong closed pull request #23193: [FLINK-32820][flink-java] Revert the ParameterTool related changes from FLINK-32558
xintongsong closed pull request #23193: [FLINK-32820][flink-java] Revert the ParameterTool related changes from FLINK-32558 URL: https://github.com/apache/flink/pull/23193 -- 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] ljw-hit commented on pull request #23162: [FLINK-32650][protobuf]Added the ability to split flink-protobuf code…
ljw-hit commented on PR #23162: URL: https://github.com/apache/flink/pull/23162#issuecomment-1676195837 @libenchao hi, If you have time recently, can you help review this code? -- 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-26358) Operator maxParallelism is lost during chaining
[ https://issues.apache.org/jira/browse/FLINK-26358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26358: --- Labels: auto-deprioritized-critical auto-deprioritized-major pull-request-available stale-minor (was: auto-deprioritized-critical auto-deprioritized-major 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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Operator maxParallelism is lost during chaining > --- > > Key: FLINK-26358 > URL: https://issues.apache.org/jira/browse/FLINK-26358 > Project: Flink > Issue Type: Bug > Components: Runtime / Coordination >Affects Versions: 1.14.3, 1.15.0 >Reporter: Fabian Paul >Priority: Minor > Labels: auto-deprioritized-critical, auto-deprioritized-major, > pull-request-available, stale-minor > > During the generation of the JobGraph from the StreamGraph the maxParallelism > of the chained operators is lost so the maxParallelism written to a snapshot > might not reflect the real maxParallelism of the operator. > If a user now unchains the operator it is not possible to restore a snapshot > anymore because the maxParallelism of the operator and the snapshot do not > match anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29579) Flink parquet reader cannot read fully optional elements in a repeated list
[
https://issues.apache.org/jira/browse/FLINK-29579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29579:
---
Labels: SchemaValidation parquet parquetReader stale-major (was:
SchemaValidation parquet parquetReader)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Flink parquet reader cannot read fully optional elements in a repeated list
> ---
>
> Key: FLINK-29579
> URL: https://issues.apache.org/jira/browse/FLINK-29579
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
>Affects Versions: 1.13.2
>Reporter: Tiansu Yu
>Priority: Major
> Labels: SchemaValidation, parquet, parquetReader, stale-major
>
> While trying to read a parquet file containing the following field as part of
> the schema,
> {code:java}
> optional group attribute_values (LIST) {
> repeated group list {
> optional group element {
> optional binary attribute_key_id (STRING);
> optional binary attribute_value_id (STRING);
> optional int32 pos;
> }
> }
> } {code}
> I encountered the following problem
> {code:java}
> Exception in thread "main" java.lang.UnsupportedOperationException: List
> field [optional binary attribute_key_id (STRING)] in List [attribute_values]
> has to be required.
> at
> org.apache.flink.formats.parquet.utils.ParquetSchemaConverter.convertGroupElementToArrayTypeInfo(ParquetSchemaConverter.java:338)
> at
> org.apache.flink.formats.parquet.utils.ParquetSchemaConverter.convertParquetTypeToTypeInfo(ParquetSchemaConverter.java:271)
> at
> org.apache.flink.formats.parquet.utils.ParquetSchemaConverter.convertFields(ParquetSchemaConverter.java:81)
> at
> org.apache.flink.formats.parquet.utils.ParquetSchemaConverter.fromParquetType(ParquetSchemaConverter.java:61)
> at
> org.apache.flink.formats.parquet.ParquetInputFormat.(ParquetInputFormat.java:120)
> at
> org.apache.flink.formats.parquet.ParquetRowInputFormat.(ParquetRowInputFormat.java:39)
> {code}
> The main code that raises the problem goes as follows:
> {code:java}
> private static ObjectArrayTypeInfo convertGroupElementToArrayTypeInfo(
> GroupType arrayFieldType, GroupType elementType) {
> for (Type type : elementType.getFields()) {
> if (!type.isRepetition(Type.Repetition.REQUIRED)) {
> throw new UnsupportedOperationException(
> String.format(
> "List field [%s] in List [%s] has to be
> required. ",
> type.toString(), arrayFieldType.getName()));
> }
> }
> return
> ObjectArrayTypeInfo.getInfoFor(convertParquetTypeToTypeInfo(elementType));
> } {code}
> I am not very familiar with internals of Parquet schema. But the problem
> looks like to me is that Flink is too restrictive on repetition types inside
> certain nested fields. Would love to hear some feedbacks on this
> (improvements, corrections / workarounds).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26499) Azure hang due to unable to download akka artifact
[
https://issues.apache.org/jira/browse/FLINK-26499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26499:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Azure hang due to unable to download akka artifact
> --
>
> Key: FLINK-26499
> URL: https://issues.apache.org/jira/browse/FLINK-26499
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines
>Affects Versions: 1.15.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> Mar 03 14:23:14 "main" #1 prio=5 os_prio=0 tid=0x7f9d8800b800 nid=0x4dc5
> in Object.wait() [0x7f9d8ebd5000]
> Mar 03 14:23:14java.lang.Thread.State: WAITING (on object monitor)
> Mar 03 14:23:14 at java.lang.Object.wait(Native Method)
> Mar 03 14:23:14 - waiting on <0x8d7e9ae0> (a
> java.lang.UNIXProcess)
> Mar 03 14:23:14 at java.lang.Object.wait(Object.java:502)
> Mar 03 14:23:14 at java.lang.UNIXProcess.waitFor(UNIXProcess.java:395)
> Mar 03 14:23:14 - locked <0x8d7e9ae0> (a java.lang.UNIXProcess)
> Mar 03 14:23:14 at
> org.apache.flink.runtime.rpc.akka.FallbackAkkaRpcSystemLoader.downloadDependencies(FallbackAkkaRpcSystemLoader.java:149)
> Mar 03 14:23:14 at
> org.apache.flink.runtime.rpc.akka.FallbackAkkaRpcSystemLoader.loadRpcSystem(FallbackAkkaRpcSystemLoader.java:75)
> Mar 03 14:23:14 at
> org.apache.flink.runtime.rpc.RpcSystem.load(RpcSystem.java:101)
> Mar 03 14:23:14 at
> org.apache.flink.runtime.rpc.RpcSystem.load(RpcSystem.java:84)
> Mar 03 14:23:14 at
> org.apache.flink.runtime.testutils.MiniClusterResource.(MiniClusterResource.java:73)
> Mar 03 14:23:14 at
> org.apache.flink.test.util.AbstractTestBase.(AbstractTestBase.java:66)
> Mar 03 14:23:14 at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> Mar 03 14:23:14 at
> sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
> Mar 03 14:23:14 at
> sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:156)
> Mar 03 14:23:14 at
> java.lang.reflect.Field.acquireFieldAccessor(Field.java:1088)
> Mar 03 14:23:14 at
> java.lang.reflect.Field.getFieldAccessor(Field.java:1069)
> Mar 03 14:23:14 at java.lang.reflect.Field.get(Field.java:393)
> Mar 03 14:23:14 at
> org.junit.runners.model.FrameworkField.get(FrameworkField.java:92)
> Mar 03 14:23:14 at
> org.junit.runners.model.TestClass.collectAnnotatedFieldValues(TestClass.java:249)
> Mar 03 14:23:14 at
> org.junit.runners.ParentRunner.classRules(ParentRunner.java:280)
> Mar 03 14:23:14 at
> org.junit.runners.ParentRunner.withClassRules(ParentRunner.java:268)
> Mar 03 14:23:14 at
> org.junit.runners.ParentRunner.classBlock(ParentRunner.java:217)
> Mar 03 14:23:14 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:412)
> Mar 03 14:23:14 at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> Mar 03 14:23:14 at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> Mar 03 14:23:14 at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
> Mar 03 14:23:14 at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> Mar 03 14:23:14 at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> Mar 03 14:23:14 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:107)
> Mar 03 14:23:14 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> Mar 03 14:23:14 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> Mar 03 14:23:14 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator$$Lambda$157/260840925.accept(Unknown
> Source)
> Mar 03 14:23:14 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> Mar 03 14:23:14 at
>
[jira] [Updated] (FLINK-32450) Update Kafka CI setup to latest version for PRs and nightly builds
[ https://issues.apache.org/jira/browse/FLINK-32450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-32450: --- 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. > Update Kafka CI setup to latest version for PRs and nightly builds > -- > > Key: FLINK-32450 > URL: https://issues.apache.org/jira/browse/FLINK-32450 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / Kafka >Reporter: Martijn Visser >Assignee: Martijn Visser >Priority: Major > Labels: pull-request-available, stale-assigned > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29553) Support UNIX_TIMESTAMP in Table API
[ https://issues.apache.org/jira/browse/FLINK-29553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-29553: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Support UNIX_TIMESTAMP in Table API > > > Key: FLINK-29553 > URL: https://issues.apache.org/jira/browse/FLINK-29553 > Project: Flink > Issue Type: Improvement >Reporter: hehuiyuan >Priority: Major > Labels: pull-request-available, stale-major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31301) Unsupported nested columns in column list of insert statement
[
https://issues.apache.org/jira/browse/FLINK-31301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31301:
---
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.
> Unsupported nested columns in column list of insert statement
> -
>
> Key: FLINK-31301
> URL: https://issues.apache.org/jira/browse/FLINK-31301
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
>Affects Versions: 1.17.0, 1.16.1
>Reporter: lincoln lee
>Assignee: Aitozi
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> Currently an error will be raised when use nested columns in column list of
> insert statement, e.g.,
> {code:java}
> INSERT INTO nested_type_sink (a,b.b1,c.c2,f)
> SELECT a,b.b1,c.c2,f FROM nested_type_src
> {code}
>
> {code:java}
> java.lang.AssertionError
> at org.apache.calcite.sql.SqlIdentifier.getSimple(SqlIdentifier.java:333)
> at
> org.apache.calcite.sql.validate.SqlValidatorUtil.getTargetField(SqlValidatorUtil.java:612)
> at
> org.apache.flink.table.planner.calcite.PreValidateReWriter$.$anonfun$appendPartitionAndNullsProjects$3(PreValidateReWriter.scala:171)
> at
> scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:233)
> at scala.collection.Iterator.foreach(Iterator.scala:937)
> at scala.collection.Iterator.foreach$(Iterator.scala:937)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1425)
> at scala.collection.IterableLike.foreach(IterableLike.scala:70)
> at scala.collection.IterableLike.foreach$(IterableLike.scala:69)
> at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> at scala.collection.TraversableLike.map(TraversableLike.scala:233)
> at scala.collection.TraversableLike.map$(TraversableLike.scala:226)
> at scala.collection.AbstractTraversable.map(Traversable.scala:104)
> at
> org.apache.flink.table.planner.calcite.PreValidateReWriter$.appendPartitionAndNullsProjects(PreValidateReWriter.scala:164)
> at
> org.apache.flink.table.planner.calcite.PreValidateReWriter.rewriteInsert(PreValidateReWriter.scala:71)
> at
> org.apache.flink.table.planner.calcite.PreValidateReWriter.visit(PreValidateReWriter.scala:61)
> at
> org.apache.flink.table.planner.calcite.PreValidateReWriter.visit(PreValidateReWriter.scala:50)
> at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:161)
> at
> org.apache.flink.table.planner.calcite.FlinkPlannerImpl.org$apache$flink$table$planner$calcite$FlinkPlannerImpl$$validate(FlinkPlannerImpl.scala:118)
> at
> org.apache.flink.table.planner.calcite.FlinkPlannerImpl.validate(FlinkPlannerImpl.scala:113)
> at
> org.apache.flink.table.planner.operations.SqlToOperationConverter.convert(SqlToOperationConverter.java:281)
> at
> org.apache.flink.table.planner.delegation.ParserImpl.parse(ParserImpl.java:106)
> at
> org.apache.flink.table.api.internal.StatementSetImpl.addInsertSql(StatementSetImpl.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-29642) MySqlCatalogITCase.testWithoutCatalogDB
[
https://issues.apache.org/jira/browse/FLINK-29642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29642:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> MySqlCatalogITCase.testWithoutCatalogDB
> ---
>
> Key: FLINK-29642
> URL: https://issues.apache.org/jira/browse/FLINK-29642
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC, Table SQL / Ecosystem
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> [This
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42011=logs=dbe51908-4958-5c8c-9557-e10952d4259d=55d11a16-067d-538d-76a3-4c096a3a8e24=15625]
> failed (not exclusively) because of
> {{MySqlCatalogITCase.testWithoutCatalogDB}} timing out.
> {code}
> Oct 14 02:18:03 "main" #1 prio=5 os_prio=0 tid=0x7fa9bc00b800 nid=0x3528
> waiting on condition [0x7fa9c54e3000]
> Oct 14 02:18:03java.lang.Thread.State: WAITING (parking)
> Oct 14 02:18:03 at sun.misc.Unsafe.park(Native Method)
> Oct 14 02:18:03 - parking to wait for <0xaaae6cd0> (a
> java.util.concurrent.CompletableFuture$Signaller)
> Oct 14 02:18:03 at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> Oct 14 02:18:03 at
> java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1707)
> Oct 14 02:18:03 at
> java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3323)
> Oct 14 02:18:03 at
> java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1742)
> Oct 14 02:18:03 at
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
> Oct 14 02:18:03 at
> org.apache.flink.streaming.api.operators.collect.CollectResultFetcher.sendRequest(CollectResultFetcher.java:170)
> Oct 14 02:18:03 at
> org.apache.flink.streaming.api.operators.collect.CollectResultFetcher.next(CollectResultFetcher.java:129)
> Oct 14 02:18:03 at
> org.apache.flink.streaming.api.operators.collect.CollectResultIterator.nextResultFromFetcher(CollectResultIterator.java:106)
> Oct 14 02:18:03 at
> org.apache.flink.streaming.api.operators.collect.CollectResultIterator.hasNext(CollectResultIterator.java:80)
> Oct 14 02:18:03 at
> org.apache.flink.table.planner.connectors.CollectDynamicSink$CloseableRowIteratorWrapper.hasNext(CollectDynamicSink.java:222)
> Oct 14 02:18:03 at
> java.util.Iterator.forEachRemaining(Iterator.java:115)
> Oct 14 02:18:03 at
> org.apache.flink.util.CollectionUtil.iteratorToList(CollectionUtil.java:115)
> Oct 14 02:18:03 at
> org.apache.flink.connector.jdbc.catalog.MySqlCatalogITCase.testWithoutCatalogDB(MySqlCatalogITCase.java:309)
> [...]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-32305) History Server is slow at starting
[ https://issues.apache.org/jira/browse/FLINK-32305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-32305: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > History Server is slow at starting > -- > > Key: FLINK-32305 > URL: https://issues.apache.org/jira/browse/FLINK-32305 > Project: Flink > Issue Type: Bug > Components: Runtime / Web Frontend >Reporter: Yiming Zang >Priority: Major > Labels: pull-request-available, stale-major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29737) Support DataGen on waveform function
[ https://issues.apache.org/jira/browse/FLINK-29737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-29737: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Support DataGen on waveform function > > > Key: FLINK-29737 > URL: https://issues.apache.org/jira/browse/FLINK-29737 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: chenzihao >Priority: Major > Labels: pull-request-available, stale-major > Attachments: image-2022-10-24-16-09-47-386.png, > image-2022-10-24-16-09-52-410.png > > > In some scenarios, we need to simulate flow changes in the production > environment. The current DATAGEN feature only supports data generation at a > constant rate. We try to simulate increments of flow using batch jobs, but > the production rate is not smooth, so I suggest that we can support sin-based > data generation in order to get smooth changes. > 1. add another batch job to simulate increments of flow. > !image-2022-10-24-16-09-52-410.png! > 2. sin-based. > !image-2022-10-24-16-09-47-386.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29893) k8s python e2e test failed due to permission error when pulling the Docker image
[
https://issues.apache.org/jira/browse/FLINK-29893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29893:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> k8s python e2e test failed due to permission error when pulling the Docker
> image
>
>
> Key: FLINK-29893
> URL: https://issues.apache.org/jira/browse/FLINK-29893
> Project: Flink
> Issue Type: Bug
> Components: Test Infrastructure
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> [This build
> failed|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42415=logs=bea52777-eaf8-5663-8482-18fbc3630e81=b2642e3a-5b86-574d-4c8a-f7e2842bfb14=11824]
> in {{test_kubernetes_pyflink_application}} due to permission issues when
> pulling the Docker image:
> {quote}
> Failed to pull image "test_kubernetes_pyflink_application": rpc error: code =
> Unknown desc = Error response from daemon: pull access denied for
> test_kubernetes_pyflink_application, repository does not exist or may require
> 'docker login': denied: requested access to the resource is denied
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30081) Local executor can not accept different jvm-overhead.min/max values
[
https://issues.apache.org/jira/browse/FLINK-30081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30081:
---
Labels: pull-request-available stale-major (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 issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Local executor can not accept different jvm-overhead.min/max values
> ---
>
> Key: FLINK-30081
> URL: https://issues.apache.org/jira/browse/FLINK-30081
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Affects Versions: 1.16.0
>Reporter: Mingliang Liu
>Priority: Major
> Labels: pull-request-available, stale-major
>
> In local executor, it's not possible to set different values for
> {{taskmanager.memory.jvm-overhead.max}} and
> {{{}taskmanager.memory.jvm-overhead.min{}}}. The same problem for
> {{taskmanager.memory.network.max}} and {{{}taskmanager.memory.network.min{}}}.
> Sample code to reproduce:
> {code:java}
> Configuration conf = new Configuration();
> conf.setString(TaskManagerOptions.JVM_OVERHEAD_MIN.key(), "1GB");
> conf.setString(TaskManagerOptions.JVM_OVERHEAD_MAX.key(), "2GB");
> StreamExecutionEnvironment.createLocalEnvironment(conf)
> .fromElements("Hello", "World")
> .executeAndCollect()
> .forEachRemaining(System.out::println); {code}
> The failing exception is something like:
> {code:java}
> Exception in thread "main" java.lang.IllegalArgumentException
> at org.apache.flink.util.Preconditions.checkArgument(Preconditions.java:122)
> at
> org.apache.flink.runtime.taskexecutor.TaskExecutorResourceUtils.calculateTotalProcessMemoryFromComponents(TaskExecutorResourceUtils.java:182)
> at
> org.apache.flink.runtime.taskexecutor.TaskExecutorMemoryConfiguration.create(TaskExecutorMemoryConfiguration.java:119)
> {code}
> I think the problem was that we expect the max and min to equal, but local
> executor did not reset them correctly?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30023) ChangelogStorageMetricsTest#testTotalAttemptsPerUpload failed
[ https://issues.apache.org/jira/browse/FLINK-30023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30023: --- Labels: pull-request-available stale-major test-stability (was: pull-request-available test-stability) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > ChangelogStorageMetricsTest#testTotalAttemptsPerUpload failed > - > > Key: FLINK-30023 > URL: https://issues.apache.org/jira/browse/FLINK-30023 > Project: Flink > Issue Type: Bug > Components: Runtime / State Backends >Affects Versions: 1.16.0, 1.17.0, 1.15.3 >Reporter: Weijie Guo >Priority: Major > Labels: pull-request-available, stale-major, test-stability > > java.util.concurrent.TimeoutException: Attempt 3 timed out after 20ms > [https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43021=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=24c3384f-1bcb-57b3-224f-51bf973bbee8=9829] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29952) Using DROP TABLE XXX to drop a temporary table （or view） in sql-client can get an exception with incomplete explaination.
[ https://issues.apache.org/jira/browse/FLINK-29952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-29952: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Using DROP TABLE XXX to drop a temporary table （or view） in sql-client can > get an exception with incomplete explaination. > - > > Key: FLINK-29952 > URL: https://issues.apache.org/jira/browse/FLINK-29952 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Affects Versions: 1.16.0 > Environment: Flink 1.16.0 > Red Hat Enterprise Linux Server release 7.4 >Reporter: StarBoy1005 >Priority: Major > Labels: pull-request-available, stale-major > Attachments: image-2022-11-09-15-06-33-188.png > > > Drop temporary table by using DROP TABLE XXX...always get "Drop it first > before removing the permanent table" but I just create a temporary table and > have no relation with any permanent table. Like the official example : > -- create a word data generator table > CREATE TEMPORARY TABLE word_table ( > word STRING > ) WITH ( > 'connector' = 'datagen', > 'fields.word.length' = '1' > ); > current exception: > !image-2022-11-09-15-06-33-188.png! > So I guess the exception should append some notice like "please check > whether miss a TEMPORARY before TABLE". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30036) Force delete pod when k8s node is not ready
[ https://issues.apache.org/jira/browse/FLINK-30036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30036: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Force delete pod when k8s node is not ready > > > Key: FLINK-30036 > URL: https://issues.apache.org/jira/browse/FLINK-30036 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes >Reporter: Peng Yuan >Priority: Major > Labels: pull-request-available, stale-major > Attachments: image-2022-11-17-10-25-59-945.png > > > When the K8s node is in the NotReady state, the taskmanager pod scheduled on > it is always in the terminating state. When the flink cluster has a strict > quota, the terminating pod will hold the resources all the time. As a result, > the new taskmanager pod cannot apply for resources and cannot be started. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29623) Bump Prometheus Java Client to 0.16.0
[ https://issues.apache.org/jira/browse/FLINK-29623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-29623: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Bump Prometheus Java Client to 0.16.0 > - > > Key: FLINK-29623 > URL: https://issues.apache.org/jira/browse/FLINK-29623 > Project: Flink > Issue Type: Technical Debt > Components: Runtime / Metrics >Reporter: Martijn Visser >Priority: Major > Labels: pull-request-available, stale-major > > Flink uses an old and no longer supported version of > io.prometheus:simpleclient. We should upgrade to the latest version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26498) The window result may not have been emitted when use window emit feature and set allow-latency
[
https://issues.apache.org/jira/browse/FLINK-26498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26498:
---
Labels: auto-deprioritized-major pull-request-available stale-minor (was:
auto-deprioritized-major 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 issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> The window result may not have been emitted when use window emit feature and
> set allow-latency
>
>
> Key: FLINK-26498
> URL: https://issues.apache.org/jira/browse/FLINK-26498
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: hehuiyuan
>Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
> Attachments: image-2022-03-05-23-53-37-086.png,
> image-2022-03-05-23-53-44-196.png, image-2022-03-06-00-03-11-670.png
>
>
> the sql of job :
> {code:java}
> CREATE TABLE tableSource(
> name string,
> age int not null,
> sex string,
> dt TIMESTAMP(3),
> WATERMARK FOR dt AS dt
> ) WITH (
> );
> CREATE TABLE tableSink(
> windowstart timestamp(3),
> windowend timestamp(3),
> name string,
> age int,
> cou bigint
> )
> WITH (
> );
> INSERT INTO tablesink
> SELECT
> TUMBLE_START(dt, INTERVAL '1' HOUR),
> TUMBLE_END(dt, INTERVAL '1' HOUR),
> name,
> age,
> count(sex)
> FROM tableSource
> GROUP BY TUMBLE(dt, INTERVAL '1' HOUR), name,age {code}
>
> and table config:
> {code:java}
> table.exec.emit.allow-lateness = 1 hour
> table.exec.emit.late-fire.delay = 1 min
> table.exec.emit.early-fire.delay = 1min{code}
>
> The data:
> {code:java}
> >hehuiyuan1,22,woman,2022-03-05 00:30:22.000
> >hehuiyuan1,22,woman,2022-03-05 00:40:22.000
> //pause ,wait for the window trigger for earlyTrigger 1 min
> >hehuiyuan1,22,woman,2022-03-05 00:50:22.000
> >hehuiyuan1,22,woman,2022-03-05 00:56:22.000
> //pause ,wait for the window trigger for earlyTrigger 1 min
> >hehuiyuan1,22,woman,2022-03-05 01:00:00.000
> //pause ,wait for the window trigger for earlyTrigger 1 min
> >hehuiyuan1,22,woman,2022-03-05 00:59:20.000 --latency data
> //pause ,wait for the window trigger for earlyTrigger 1 min
> >hehuiyuan1,22,woman,2022-03-05 00:59:20.100 --latency data
> >hehuiyuan1,22,woman,2022-03-05 02:00:00.000 -- window state clean for
> >[0:00:00 1:00:00]
> >hehuiyuan1,22,woman,2022-03-05 02:10:00.000 {code}
>
> The result:
> {code:java}
> > +I(+I[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 2])
> > -U(-U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 2])
> > +U(+U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 4])
> > +I(+I[2022-03-05T01:00, 2022-03-05T02:00, hehuiyuan1, 22, 1])
> > -U(-U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 4])
> > +U(+U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 5])
>
>
> > +I(+I[2022-03-05T02:00, 2022-03-05T03:00, hehuiyuan1, 22, 2]) {code}
>
> The window result is lost when `hehuiyuan1,22,woman,2022-03-05 00:59:20.100`
> arrived， the lateTrigger is not trigger and the window[0:00:00 ,1:00:00] is
> cleaned when the data `hehuiyuan1,22,woman,2022-03-05 02:00:00.000` arrived
> that updated watermark.
>
> The window[0:00:00 ,1:00:00] has 6 pieces of data, but we got 5.
> The trigger is AfterEndOfWindowEarlyAndLate .
> So WindowOpearator may need to emit reuslt when the window cleanupTimer call
> onEventTime.
>
> I think the correct result is as follows:
> {code:java}
> > +I(+I[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 2])
> > -U(-U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 2])
> > +U(+U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 4])
> > +I(+I[2022-03-05T01:00, 2022-03-05T02:00, hehuiyuan1, 22, 1])
> > -U(-U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 4])
> > +U(+U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 5])
> > -U(-U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 5])
> > +U(+U[2022-03-05T00:00, 2022-03-05T01:00, hehuiyuan1, 22, 6])
> > +I(+I[2022-03-05T02:00, 2022-03-05T03:00, hehuiyuan1, 22, 2]) {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-29980) Wrap the HiveSource's bulkFormat to handle the partition keys
[
https://issues.apache.org/jira/browse/FLINK-29980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29980:
---
Labels: pull-request-available stale-major (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 issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Wrap the HiveSource's bulkFormat to handle the partition keys
> -
>
> Key: FLINK-29980
> URL: https://issues.apache.org/jira/browse/FLINK-29980
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Hive
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available, stale-major
>
> As described in https://issues.apache.org/jira/browse/FLINK-25113 to clean up
> the partition keys logic in the parquet and orc formats, hive source should
> leverage the {{FileInfoExtractorBulkFormat}} to handle the partition keys
> internally
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-29587) Fail to generate code for SearchOperator
[
https://issues.apache.org/jira/browse/FLINK-29587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29587:
---
Labels: pull-request-available stale-major (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 issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Fail to generate code for SearchOperator
> --
>
> Key: FLINK-29587
> URL: https://issues.apache.org/jira/browse/FLINK-29587
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner, Table SQL / Runtime
>Reporter: luoyuxia
>Priority: Major
> Labels: pull-request-available, stale-major
>
> Can be reproduced with the following code with Hive dialect
> {code:java}
> // hive dialect
> tableEnv.executeSql("create table table1 (id int, val string, val1 string,
> dimid int)");
> tableEnv.executeSql("create table table3 (id int)");
> CollectionUtil.iteratorToList(
> tableEnv.executeSql(
> "select table1.id, table1.val, table1.val1 from
> table1 left semi join"
> + " table3 on table1.dimid = table3.id and
> table3.id = 100 where table1.dimid = 200")
> .collect());{code}
> The plan is
> {code:java}
> LogicalSink(table=[*anonymous_collect$1*], fields=[id, val, val1])
> LogicalProject(id=[$0], val=[$1], val1=[$2])
> LogicalFilter(condition=[=($3, 200)])
> LogicalJoin(condition=[AND(=($3, $4), =($4, 100))], joinType=[semi])
> LogicalTableScan(table=[[test-catalog, default, table1]])
> LogicalTableScan(table=[[test-catalog, default,
> table3]])BatchPhysicalSink(table=[*anonymous_collect$1*], fields=[id, val,
> val1])
> BatchPhysicalNestedLoopJoin(joinType=[LeftSemiJoin], where=[$f1],
> select=[id, val, val1], build=[right])
> BatchPhysicalCalc(select=[id, val, val1], where=[=(dimid, 200)])
> BatchPhysicalTableSourceScan(table=[[test-catalog, default, table1]],
> fields=[id, val, val1, dimid])
> BatchPhysicalExchange(distribution=[broadcast])
> BatchPhysicalCalc(select=[SEARCH(id, Sarg[]) AS $f1])
> BatchPhysicalTableSourceScan(table=[[test-catalog, default, table3]],
> fields=[id]) {code}
>
> But it'll throw exception when generate code for it.
> The exception is
>
>
> {code:java}
> java.util.NoSuchElementException
> at
> com.google.common.collect.ImmutableRangeSet.span(ImmutableRangeSet.java:203)
> at org.apache.calcite.util.Sarg.isComplementedPoints(Sarg.java:148)
> at
> org.apache.flink.table.planner.codegen.calls.SearchOperatorGen$.generateSearch(SearchOperatorGen.scala:87)
> at
> org.apache.flink.table.planner.codegen.ExprCodeGenerator.visitCall(ExprCodeGenerator.scala:474)
> at
> org.apache.flink.table.planner.codegen.ExprCodeGenerator.visitCall(ExprCodeGenerator.scala:57)
> at org.apache.calcite.rex.RexCall.accept(RexCall.java:174)
> at
> org.apache.flink.table.planner.codegen.ExprCodeGenerator.generateExpression(ExprCodeGenerator.scala:143)
> at
> org.apache.flink.table.planner.codegen.CalcCodeGenerator$.$anonfun$generateProcessCode$4(CalcCodeGenerator.scala:140)
> at
> scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:233)
> at
> scala.collection.mutable.ResizableArray.foreach(ResizableArray.scala:58)
> at
> scala.collection.mutable.ResizableArray.foreach$(ResizableArray.scala:51)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
> at scala.collection.TraversableLike.map(TraversableLike.scala:233)
> at scala.collection.TraversableLike.map$(TraversableLike.scala:226)
> at scala.collection.AbstractTraversable.map(Traversable.scala:104)
> at
> org.apache.flink.table.planner.codegen.CalcCodeGenerator$.produceProjectionCode$1(CalcCodeGenerator.scala:140)
> at
> org.apache.flink.table.planner.codegen.CalcCodeGenerator$.generateProcessCode(CalcCodeGenerator.scala:164)
> at
> org.apache.flink.table.planner.codegen.CalcCodeGenerator$.generateCalcOperator(CalcCodeGenerator.scala:49)
> at
> org.apache.flink.table.planner.codegen.CalcCodeGenerator.generateCalcOperator(CalcCodeGenerator.scala)
> at
> org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecCalc.translateToPlanInternal(CommonExecCalc.java:100)
> at
> org.apache.flink.table.planner.plan.nodes.exec.ExecNodeBase.translateToPlan(ExecNodeBase.java:158)
> at
>
[jira] [Updated] (FLINK-31261) Make AdaptiveScheduler aware of the (local) state size
[ https://issues.apache.org/jira/browse/FLINK-31261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31261: --- 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. > Make AdaptiveScheduler aware of the (local) state size > -- > > Key: FLINK-31261 > URL: https://issues.apache.org/jira/browse/FLINK-31261 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Affects Versions: 1.18.0 >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.18.0 > > > FLINK-21450 makes the Adaptive Schulder aware of Local Recovery. > Each slot-group pair is assigned a score based on a keyGroupRange size. > That score isn't always optimlal - it could be improved by computing the > score based on the actual state size on disk. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26091) SafetyNetCloseableRegistryTest.testNonBlockingClose failed on azure
[
https://issues.apache.org/jira/browse/FLINK-26091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26091:
---
Labels: auto-deprioritized-major stale-critical test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> SafetyNetCloseableRegistryTest.testNonBlockingClose failed on azure
> ---
>
> Key: FLINK-26091
> URL: https://issues.apache.org/jira/browse/FLINK-26091
> Project: Flink
> Issue Type: Bug
> Components: API / Core
>Affects Versions: 1.14.3, 1.15.3
>Reporter: Yun Gao
>Priority: Critical
> Labels: auto-deprioritized-major, stale-critical, test-stability
>
> {code:java}
> Feb 11 02:11:41 [INFO] Running
> org.apache.flink.core.fs.SafetyNetCloseableRegistryTest
> Feb 11 02:11:45 [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0,
> Time elapsed: 3.188 s <<< FAILURE! - in
> org.apache.flink.core.fs.SafetyNetCloseableRegistryTest
> Feb 11 02:11:45 [ERROR] testNonBlockingClose Time elapsed: 0.265 s <<<
> FAILURE!
> Feb 11 02:11:45 org.opentest4j.MultipleFailuresError:
> Feb 11 02:11:45 Multiple Failures (2 failures)
> Feb 11 02:11:45 java.lang.AssertionError: Closed registry should not
> accept closeables!
> Feb 11 02:11:45 java.lang.AssertionError:
> Feb 11 02:11:45 at
> org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
> Feb 11 02:11:45 at
> org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
> Feb 11 02:11:45 at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
> Feb 11 02:11:45 at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
> Feb 11 02:11:45 at
> org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
> Feb 11 02:11:45 at
> org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
> Feb 11 02:11:45 at
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
> Feb 11 02:11:45 at
> org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
> Feb 11 02:11:45 at
> org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:372)
> Feb 11 02:11:45 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> Feb 11 02:11:45 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Feb 11 02:11:45 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> Feb 11 02:11:45 at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> Feb 11 02:11:45 at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> Feb 11 02:11:45 at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> Feb 11 02:11:45 at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> Feb 11 02:11:45 at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> Feb 11 02:11:45 at
> java.util.Iterator.forEachRemaining(Iterator.java:116)
> Feb 11 02:11:45 at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> Feb 11 02:11:45 at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> Feb 11 02:11:45 at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> Feb 11 02:11:45 at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> Feb 11
[jira] [Updated] (FLINK-26272) Elasticsearch7SinkITCase.testWriteJsonToElasticsearch fails with socket timeout
[
https://issues.apache.org/jira/browse/FLINK-26272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26272:
---
Labels: auto-deprioritized-critical auto-deprioritized-major stale-minor
test-stability (was: auto-deprioritized-critical auto-deprioritized-major
test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Elasticsearch7SinkITCase.testWriteJsonToElasticsearch fails with socket
> timeout
> ---
>
> Key: FLINK-26272
> URL: https://issues.apache.org/jira/browse/FLINK-26272
> Project: Flink
> Issue Type: Bug
> Components: Connectors / ElasticSearch
>Affects Versions: 1.15.0
>Reporter: Matthias Pohl
>Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> stale-minor, test-stability
>
> We observed a test failure in [this
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31883=logs=d44f43ce-542c-597d-bf94-b0718c71e5e8=ed165f3f-d0f6-524b-5279-86f8ee7d0e2d=12917]
> with {{Elasticsearch7SinkITCase.testWriteJsonToElasticsearch}} failing due
> to a {{SocketTimeoutException}}:
> {code}
> Feb 18 18:04:20 [ERROR] Tests run: 6, Failures: 0, Errors: 1, Skipped: 0,
> Time elapsed: 80.248 s <<< FAILURE! - in
> org.apache.flink.connector.elasticsearch.sink.Elasticsearch7SinkITCase
> Feb 18 18:04:20 [ERROR]
> org.apache.flink.connector.elasticsearch.sink.Elasticsearch7SinkITCase.testWriteJsonToElasticsearch(BiFunction)[1]
> Time elapsed: 31.525 s <<< ERROR!
> Feb 18 18:04:20 org.apache.flink.runtime.client.JobExecutionException: Job
> execution failed.
> Feb 18 18:04:20 at
> org.apache.flink.runtime.jobmaster.JobResult.toJobExecutionResult(JobResult.java:144)
> Feb 18 18:04:20 at
> org.apache.flink.runtime.minicluster.MiniClusterJobClient.lambda$getJobExecutionResult$3(MiniClusterJobClient.java:141)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:616)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
> Feb 18 18:04:20 at
> org.apache.flink.runtime.rpc.akka.AkkaInvocationHandler.lambda$invokeRpc$1(AkkaInvocationHandler.java:259)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
> Feb 18 18:04:20 at
> org.apache.flink.util.concurrent.FutureUtils.doForward(FutureUtils.java:1389)
> Feb 18 18:04:20 at
> org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.lambda$null$1(ClassLoadingUtils.java:93)
> Feb 18 18:04:20 at
> org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:68)
> Feb 18 18:04:20 at
> org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.lambda$guardCompletionWithContextClassLoader$2(ClassLoadingUtils.java:92)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
> Feb 18 18:04:20 at
> java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
> Feb 18 18:04:20 at
> org.apache.flink.runtime.concurrent.akka.AkkaFutureUtils$1.onComplete(AkkaFutureUtils.java:47)
> Feb 18 18:04:20 at akka.dispatch.OnComplete.internal(Future.scala:300)
> Feb 18 18:04:20 at akka.dispatch.OnComplete.internal(Future.scala:297)
> Feb 18 18:04:20 at
> akka.dispatch.japi$CallbackBridge.apply(Future.scala:224)
> Feb 18 18:04:20 at
> akka.dispatch.japi$CallbackBridge.apply(Future.scala:221)
> Feb 18 18:04:20
[jira] [Updated] (FLINK-26315) Stream job which have multily region would not recover when connection with zookeeper/hbase lost.
[
https://issues.apache.org/jira/browse/FLINK-26315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26315:
---
Labels: auto-deprioritized-critical auto-deprioritized-major
failure-recovery restart stale-minor (was: auto-deprioritized-critical
auto-deprioritized-major failure-recovery restart)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Stream job which have multily region would not recover when connection with
> zookeeper/hbase lost.
> -
>
> Key: FLINK-26315
> URL: https://issues.apache.org/jira/browse/FLINK-26315
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
>Affects Versions: 1.12.0
>Reporter: Janick Wu
>Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> failure-recovery, restart, stale-minor
> Attachments:
> [FLINK-26315]_improve_failure-rate_restart_strategy,_support_same_failure_cause_ignore.patch
>
>
> Our platfrom use failure-rate (failure-rate-interval:
> 5min,max-failures-per-interval: 6) as default restart-strategy. And
> failover-strategy is region level.
> Let's asume a job with concurrency of 10, all the edges in stream graph is
> FORWARD, then the region count is equal to job parallelism. If more than 5
> Task failed caused by connection lost between Taskmanager and external System
> such as zookeeper、hbase, failure rate will exceeded immediately. So our job
> will never recover from such situition(very common when use zookeeper for ha).
> h2. possible solution：
> Imporve failure-rate strategy: record last task failure cause and timestamp,.
> If the task failure cause occur multiple times in a short period of time, it
> will ingore the rest.
> I already implement it and work well.
> useage:
> {quote}restart-strategy: failure-rate
> restart-strategy.failure-rate.cause.insensitive: true
> restart-strategy.failure-rate.cause.insensitive-interval: 1min
> {quote}
> this configure will ignore continuously repeating exception in 1min.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-29770) hbase connector supports out-of-order data
[ https://issues.apache.org/jira/browse/FLINK-29770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-29770: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > hbase connector supports out-of-order data > -- > > Key: FLINK-29770 > URL: https://issues.apache.org/jira/browse/FLINK-29770 > Project: Flink > Issue Type: Improvement > Components: Connectors / HBase >Reporter: Bo Cui >Priority: Major > Labels: pull-request-available, stale-major > > The data may be out of order and has no timestamp. As a result, the data > written to the HBase is incorrect -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29956) Kafka-related test infrastructure code is scattered over multiple classes/environments
[
https://issues.apache.org/jira/browse/FLINK-29956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29956:
---
Labels: stale-major starter (was: starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Kafka-related test infrastructure code is scattered over multiple
> classes/environments
> --
>
> Key: FLINK-29956
> URL: https://issues.apache.org/jira/browse/FLINK-29956
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Kafka
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, starter
>
> We had a few issues with the test stability of Kafka-related tests
> (FLINK-24119, FLINK-29914). A workaround was to add randomness to topic
> identifiers. This change required touching multiple code locations that made
> it obvious that there is some room for improvement (see [Gabor's
> comment|https://github.com/apache/flink/pull/21247#issuecomment-1307084416]
> comment in the related PR). We could put some effort into unifying this by
> providing a common test environment that provides utility methods he
> mentioned in his comment:
> {quote}
> Topic creation
> Topic deletion
> Random name generation
> AdminClient creation
> Consumer creation
> Producer creation
> {quote}
> Currently, we have Kafka instances created in different locations in our test
> suite (e.g. {{KafkaSourceTestEnv}}, {{KafkaTestEnvironmentImpl}},
> {{KafkaTableTestBase}}). One idea is to provide a JUnit5 extension for this
> similarly to what we do with the
> [MiniClusterExtension|https://github.com/apache/flink/blob/a6db6ee5d0d6e9b50c6d110793e2efbd0d57cc38/flink-test-utils-parent/flink-test-utils/src/main/java/org/apache/flink/test/junit5/MiniClusterExtension.java]
> for Flink. Maybe, there's already something out there that can be
> used/extended.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26341) ZooKeeperTestEnvironment does not allow for repeated test execution
[
https://issues.apache.org/jira/browse/FLINK-26341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26341:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> ZooKeeperTestEnvironment does not allow for repeated test execution
> ---
>
> Key: FLINK-26341
> URL: https://issues.apache.org/jira/browse/FLINK-26341
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.13.6, 1.14.3, 1.15.0
>Reporter: Matthias Pohl
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {{ZooKeeperTestEnvironment.deleteAll}} fails when rerunning a test due to the
> client not being started:
> {code}
> java.lang.IllegalStateException: Client is not started
> at
> org.apache.flink.shaded.curator5.org.apache.curator.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:507)
> at
> org.apache.flink.shaded.curator5.org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:139)
> at
> org.apache.flink.runtime.zookeeper.ZooKeeperTestEnvironment.deleteAll(ZooKeeperTestEnvironment.java:145)
> at
> org.apache.flink.runtime.checkpoint.ZooKeeperCheckpointIDCounterITCase.cleanUp(ZooKeeperCheckpointIDCounterITCase.java:48)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [...]
> {code}
> This behavior was observed when running various tests with
> repeat-until-failure enabled in Intellij:
> * {{ZooKeeperCheckpointIDCounterITCase.testShutdownRemovesState}}
> * {{ZooKeeperStateHandleStoreTest.testAddAndLock}}
> *
> {{ZooKeeperStateHandleStoreTest.testFailingAddWithPossiblyInconsistentState}}
> I'd assume that this applies in any other case as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-29594) RMQSourceITCase.testMessageDelivery timed out
[
https://issues.apache.org/jira/browse/FLINK-29594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29594:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> RMQSourceITCase.testMessageDelivery timed out
> -
>
> Key: FLINK-29594
> URL: https://issues.apache.org/jira/browse/FLINK-29594
> Project: Flink
> Issue Type: Bug
> Components: Connectors/ RabbitMQ
>Affects Versions: rabbitmq-3.0.1
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> [This
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=41843=logs=fc7981dc-d266-55b0-5fff-f0d0a2294e36=1a9b228a-3e0e-598f-fc81-c321539dfdbf=38211]
> failed (not exclusively) due to {{RMQSourceITCase.testMessageDelivery}}
> timing out.
> I wasn't able to reproduce it locally with 200 test runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31360) Running HsResultPartitionTest repeatedly causes error with 137 exit code indicating a memory leak
[
https://issues.apache.org/jira/browse/FLINK-31360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31360:
---
Labels: pull-request-available stale-assigned test-stability (was:
pull-request-available test-stability)
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.
> Running HsResultPartitionTest repeatedly causes error with 137 exit code
> indicating a memory leak
> --
>
> Key: FLINK-31360
> URL: https://issues.apache.org/jira/browse/FLINK-31360
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.18.0
>Reporter: Matthias Pohl
>Assignee: Weijie Guo
>Priority: Major
> Labels: pull-request-available, stale-assigned, test-stability
> Attachments: Screenshot from 2023-03-09 13-33-37.png
>
>
> I ran {{HsResultPartitionTest}} repeatedly locally. It caused errors with an
> 137 exit consistently indicating that there might be some memory leak.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31259) Gateway supports initialization of catalog at startup
[ https://issues.apache.org/jira/browse/FLINK-31259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31259: --- 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. > Gateway supports initialization of catalog at startup > - > > Key: FLINK-31259 > URL: https://issues.apache.org/jira/browse/FLINK-31259 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Gateway >Affects Versions: 1.18.0 >Reporter: Fang Yong >Assignee: Fang Yong >Priority: Major > Labels: pull-request-available, stale-assigned > > Support to initializing catalogs in gateway when it starts -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26490) Adjust the MaxParallelism or remove the MaxParallelism check when unnecessary.
[ https://issues.apache.org/jira/browse/FLINK-26490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26490: --- Labels: auto-deprioritized-major pull-request-available stale-minor (was: auto-deprioritized-major 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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Adjust the MaxParallelism or remove the MaxParallelism check when unnecessary. > -- > > Key: FLINK-26490 > URL: https://issues.apache.org/jira/browse/FLINK-26490 > Project: Flink > Issue Type: Improvement > Components: Runtime / State Backends >Reporter: chenfengLiu >Priority: Minor > Labels: auto-deprioritized-major, pull-request-available, > stale-minor > > Since Flink introduce key group and MaxParallelism, Flink can rescale with > less cost. > But when we want to update the job parallelism bigger than the > MaxParallelism, it 's impossible cause there are so many MaxParallelism check > that require new parallelism should not bigger than MaxParallelism. > Actually, when an operator which don't contain keyed state, there should be > no problem when update the parallelism bigger than the MaxParallelism,, cause > only keyed state need MaxParallelism and key group. > So should we remove this check or auto adjust the MaxParallelism when we > restore an operator state that don't contain keyed state? > It can make job restore from checkpoint easier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26459) Streaming File Sink s3 end-to-end test failed on azure due to not enough resource
[
https://issues.apache.org/jira/browse/FLINK-26459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26459:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Streaming File Sink s3 end-to-end test failed on azure due to not enough
> resource
> -
>
> Key: FLINK-26459
> URL: https://issues.apache.org/jira/browse/FLINK-26459
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.15.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> [https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=32459=logs=af184cdd-c6d8-5084-0b69-7e9c67b35f7a=160c9ae5-96fd-516e-1c91-deb81f59292a=2859]
> {code:java}
> Digest:
> sha256:a61ed0bca213081b64be94c5e1b402ea58bc549f457c2682a86704dd55231e09
> Status: Downloaded newer image for stedolan/jq:latest
> Mar 03 03:44:51 Number of produced values 13161/6
> Mar 03 03:58:11 Test (pid: 119568) did not finish after 900 seconds. {code}
> This test first tried to kill & restart 1 TM, then kill & restart 2 TM. After
> them there should still be 4 TM, but from the log it seems only 2 remaining:
> {code:java}
> 2022-03-03 03:58:20,707 WARN
> org.apache.flink.runtime.resourcemanager.slotmanager.DeclarativeSlotManager
> [] - Could not fulfill resource requirements of job
> be4a30280fdc43d689d06ec02846e2e6. Free slots: 0
> 2022-03-03 03:58:20,707 WARN
> org.apache.flink.runtime.jobmaster.slotpool.DeclarativeSlotPoolBridge [] -
> Could not acquire the minimum required resources, failing slot requests.
> Acquired: [ResourceRequirement{resourceProfile=ResourceProfile{cpuCores=1,
> taskHeapMemory=384.000mb (402653174 bytes), taskOffHeapMemory=0 bytes,
> managedMemory=512.000mb (536870920 bytes), networkMemory=128.000mb (134217730
> bytes)}, numberOfRequiredSlots=2}]. Current slot pool status: Registered TMs:
> 2, registered slots: 2 free slots: 0
> 2022-03-03 03:58:20,708 INFO
> org.apache.flink.runtime.executiongraph.ExecutionGraph [] - Sink:
> Unnamed (2/4) (0c9ff357e74f9a97559152d5de065ae5) switched from SCHEDULED to
> FAILED on [unassigned resource].
> org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException:
> Could not acquire the minimum required resources. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26533) KafkaSinkITCase.testRecoveryWithExactlyOnceGuarantee failed on azure due to delete topic timeout
[
https://issues.apache.org/jira/browse/FLINK-26533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26533:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> KafkaSinkITCase.testRecoveryWithExactlyOnceGuarantee failed on azure due to
> delete topic timeout
>
>
> Key: FLINK-26533
> URL: https://issues.apache.org/jira/browse/FLINK-26533
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.14.3
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> Mar 07 02:42:17 [ERROR] Tests run: 8, Failures: 0, Errors: 1, Skipped: 0,
> Time elapsed: 174.077 s <<< FAILURE! - in
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase
> Mar 07 02:42:17 [ERROR] testRecoveryWithAtLeastOnceGuarantee Time elapsed:
> 63.913 s <<< ERROR!
> Mar 07 02:42:17 java.util.concurrent.TimeoutException
> Mar 07 02:42:17 at
> org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:108)
> Mar 07 02:42:17 at
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:272)
> Mar 07 02:42:17 at
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase.deleteTestTopic(KafkaSinkITCase.java:429)
> Mar 07 02:42:17 at
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase.tearDown(KafkaSinkITCase.java:160)
> Mar 07 02:42:17 at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Mar 07 02:42:17 at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Mar 07 02:42:17 at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Mar 07 02:42:17 at
> java.base/java.lang.reflect.Method.invoke(Method.java:566)
> Mar 07 02:42:17 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> Mar 07 02:42:17 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> Mar 07 02:42:17 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> Mar 07 02:42:17 at
> org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
> Mar 07 02:42:17 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> Mar 07 02:42:17 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> Mar 07 02:42:17 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> Mar 07 02:42:17 at
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> Mar 07 02:42:17 at
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Mar 07 02:42:17 at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> Mar 07 02:42:17 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> Mar 07 02:42:17 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> Mar 07 02:42:17 at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> Mar 07 02:42:17 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> Mar 07 02:42:17 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> Mar 07 02:42:17 at
> org.testcontainers.containers.FailureDetectingExternalResource$1.evaluate(FailureDetectingExternalResource.java:30)
> Mar 07 02:42:17 at
[jira] [Updated] (FLINK-26563) HadoopS3RecoverableWriterITCase hang on azure
[
https://issues.apache.org/jira/browse/FLINK-26563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26563:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> HadoopS3RecoverableWriterITCase hang on azure
> -
>
> Key: FLINK-26563
> URL: https://issues.apache.org/jira/browse/FLINK-26563
> Project: Flink
> Issue Type: Bug
> Components: FileSystems
>Affects Versions: 1.15.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> 2022-03-09T09:44:11.6454998Z Mar 09 09:44:11 "main" #1 prio=5 os_prio=0
> tid=0x7f331000b800 nid=0x7601 runnable [0x7f3318203000]
> 2022-03-09T09:44:11.6455475Z Mar 09 09:44:11java.lang.Thread.State:
> RUNNABLE
> 2022-03-09T09:44:11.6455962Z Mar 09 09:44:11 at
> java.net.SocketInputStream.socketRead0(Native Method)
> 2022-03-09T09:44:11.6456563Z Mar 09 09:44:11 at
> java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> 2022-03-09T09:44:11.6457422Z Mar 09 09:44:11 at
> java.net.SocketInputStream.read(SocketInputStream.java:171)
> 2022-03-09T09:44:11.6458036Z Mar 09 09:44:11 at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 2022-03-09T09:44:11.6458667Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:457)
> 2022-03-09T09:44:11.6459649Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketInputRecord.decodeInputRecord(SSLSocketInputRecord.java:237)
> 2022-03-09T09:44:11.6460672Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:190)
> 2022-03-09T09:44:11.6461267Z Mar 09 09:44:11 at
> sun.security.ssl.SSLTransport.decode(SSLTransport.java:109)
> 2022-03-09T09:44:11.6462110Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1386)
> 2022-03-09T09:44:11.6463039Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1354)
> 2022-03-09T09:44:11.6464168Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketImpl.access$300(SSLSocketImpl.java:73)
> 2022-03-09T09:44:11.6465097Z Mar 09 09:44:11 at
> sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:948)
> 2022-03-09T09:44:11.6466100Z Mar 09 09:44:11 at
> org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137)
> 2022-03-09T09:44:11.6467149Z Mar 09 09:44:11 at
> org.apache.http.impl.io.SessionInputBufferImpl.read(SessionInputBufferImpl.java:197)
> 2022-03-09T09:44:11.6468145Z Mar 09 09:44:11 at
> org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:176)
> 2022-03-09T09:44:11.6469179Z Mar 09 09:44:11 at
> org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135)
> 2022-03-09T09:44:11.6470153Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
> 2022-03-09T09:44:11.6471929Z Mar 09 09:44:11 at
> com.amazonaws.event.ProgressInputStream.read(ProgressInputStream.java:180)
> 2022-03-09T09:44:11.6472974Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
> 2022-03-09T09:44:11.6474107Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
> 2022-03-09T09:44:11.6474724Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
> 2022-03-09T09:44:11.6475308Z Mar 09 09:44:11 at
> com.amazonaws.event.ProgressInputStream.read(ProgressInputStream.java:180)
> 2022-03-09T09:44:11.6475917Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
> 2022-03-09T09:44:11.6476713Z Mar 09 09:44:11 at
> com.amazonaws.util.LengthCheckInputStream.read(LengthCheckInputStream.java:107)
> 2022-03-09T09:44:11.6477327Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
> 2022-03-09T09:44:11.6478193Z Mar 09 09:44:11 at
> com.amazonaws.services.s3.internal.S3AbortableInputStream.read(S3AbortableInputStream.java:125)
> 2022-03-09T09:44:11.6478853Z Mar 09 09:44:11 at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:90)
>
[jira] [Updated] (FLINK-31366) Exception is thrown when s3a and s3p are used together
[
https://issues.apache.org/jira/browse/FLINK-31366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31366:
---
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.
> Exception is thrown when s3a and s3p are used together
> --
>
> Key: FLINK-31366
> URL: https://issues.apache.org/jira/browse/FLINK-31366
> Project: Flink
> Issue Type: Bug
> Components: FileSystems
>Reporter: Hangxiang Yu
>Assignee: Hangxiang Yu
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> h3. Exception
> When s3a and s3p plugins exist at the same time, an exception will be thrown
> as below:
> {code:java}
> Caused by:java.lang.NoSuchMethodError:
> org.apache.flink.fs.s3.common.AbstractS3FileSystemFactory.
> (Ljava/lang/String;Lorg/apache/flink/fs/s3presto/common/HadoopConfigLoader;)
> {code}
> h3. Why
> In the construction method of AbstractS3FileSystemFactory, s3a shades
> HadoopConfigLoader into
> org.apache.flink.fs.s3hadoop.common.HadoopConfigLoader, and s3p shades
> HadoopConfigLoader into org.
> apache.flink.fs.s3presto.common.HadoopConfigLoader when package.
> (see shade-plugin)
>
> But the AbstractS3FileSystemFactory class will only be loaded once when
> loading even if there are two plugins.
> So it may first uses s3a plugin to load AbstractS3FileSystemFactory, and the
> construction method is loaded into AbstractS3FileSystemFactory(String name,
> org.apache. flink.fs.s3hadoop.common.HadoopConfigLoader hadoopConfigLoader),
> at this time s3p will be abnormal when it is constructed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26386) CassandraConnectorITCase.testCassandraTableSink failed on azure
[
https://issues.apache.org/jira/browse/FLINK-26386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26386:
---
Labels: auto-deprioritized-critical auto-deprioritized-major stale-minor
test-stability (was: auto-deprioritized-critical auto-deprioritized-major
test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> CassandraConnectorITCase.testCassandraTableSink failed on azure
> ---
>
> Key: FLINK-26386
> URL: https://issues.apache.org/jira/browse/FLINK-26386
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Cassandra
>Affects Versions: 1.13.6, 1.15.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> stale-minor, test-stability
>
> {code:java}
> Feb 28 02:39:19 [ERROR] Tests run: 20, Failures: 0, Errors: 1, Skipped: 0,
> Time elapsed: 226.77 s <<< FAILURE! - in
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorITCase
> Feb 28 02:39:19 [ERROR]
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorITCase.testCassandraTableSink
> Time elapsed: 52.49 s <<< ERROR!
> Feb 28 02:39:19
> com.datastax.driver.core.exceptions.InvalidConfigurationInQueryException:
> Keyspace flink doesn't exist
> Feb 28 02:39:19 at
> com.datastax.driver.core.exceptions.InvalidConfigurationInQueryException.copy(InvalidConfigurationInQueryException.java:37)
> Feb 28 02:39:19 at
> com.datastax.driver.core.exceptions.InvalidConfigurationInQueryException.copy(InvalidConfigurationInQueryException.java:27)
> Feb 28 02:39:19 at
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
> Feb 28 02:39:19 at
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
> Feb 28 02:39:19 at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:63)
> Feb 28 02:39:19 at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:39)
> Feb 28 02:39:19 at
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorITCase.createTable(CassandraConnectorITCase.java:391)
> Feb 28 02:39:19 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> Feb 28 02:39:19 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Feb 28 02:39:19 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Feb 28 02:39:19 at java.lang.reflect.Method.invoke(Method.java:498)
> Feb 28 02:39:19 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> Feb 28 02:39:19 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> Feb 28 02:39:19 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> Feb 28 02:39:19 at
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> Feb 28 02:39:19 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> Feb 28 02:39:19 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> Feb 28 02:39:19 at
> org.apache.flink.testutils.junit.RetryRule$RetryOnExceptionStatement.evaluate(RetryRule.java:192)
> Feb 28 02:39:19 at
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> Feb 28 02:39:19 at
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> Feb 28 02:39:19 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Feb 28 02:39:19 at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> Feb 28 02:39:19 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> Feb 28 02:39:19 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> Feb 28 02:39:19 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> Feb 28 02:39:19 at
> org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> Feb 28 02:39:19 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> Feb 28 02:39:19 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> Feb 28
[jira] [Updated] (FLINK-31262) Move kafka sql connector fat jar test to SmokeKafkaITCase
[
https://issues.apache.org/jira/browse/FLINK-31262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31262:
---
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.
> Move kafka sql connector fat jar test to SmokeKafkaITCase
> -
>
> Key: FLINK-31262
> URL: https://issues.apache.org/jira/browse/FLINK-31262
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka, Tests
>Reporter: Weijie Guo
>Assignee: Weijie Guo
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> {{SmokeKafkaITCase}} only covered the application packaging test of
> datastream job, we should also bring this kind of test to sql job submitted
> by sql-client to cover the case of sql connector fat jar.
> In fact, we already have similar test class with the same purpose, that is
> {{SQLClientKafkaITCase}}, but this test is ignored since 2021/4/20. It depend
> on the
> {{LocalStandaoneKafkaResource}} which download {{kafka}} and sets up a local
> cluster, but we often encounter download failures in CI environments.
> Fortunately, now we prefer to use {{TestContainer}} in E2E test. So I suggest
> integrating the corresponding test logic into {{SmokeKafkaITCase}}, and then
> removing it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31344) Support to update nested columns in update statement
[
https://issues.apache.org/jira/browse/FLINK-31344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31344:
---
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.
> Support to update nested columns in update statement
>
>
> Key: FLINK-31344
> URL: https://issues.apache.org/jira/browse/FLINK-31344
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
>Reporter: luoyuxia
>Assignee: Aitozi
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> Currently, it'll throw exception while using update statement to update
> nested column;
> For the following sql:
>
> {code:java}
> create table (t ROW<`a` INT>) with (xxx);
> update t set s.a = 1;{code}
> It'll throw the exception:
> {code:java}
> Caused by: org.apache.flink.sql.parser.impl.ParseException: Encountered "."
> at line 1, column 15.
> Was expecting:
> "=" ...
>
> at
> org.apache.flink.sql.parser.impl.FlinkSqlParserImpl.generateParseException(FlinkSqlParserImpl.java:46382)
> at
> org.apache.flink.sql.parser.impl.FlinkSqlParserImpl.jj_consume_token(FlinkSqlParserImpl.java:46190)
> at
> org.apache.flink.sql.parser.impl.FlinkSqlParserImpl.SqlUpdate(FlinkSqlParserImpl.java:14389)
> at
> org.apache.flink.sql.parser.impl.FlinkSqlParserImpl.SqlStmt(FlinkSqlParserImpl.java:4121)
> at
> org.apache.flink.sql.parser.impl.FlinkSqlParserImpl.SqlStmtList(FlinkSqlParserImpl.java:2998)
> at
> org.apache.flink.sql.parser.impl.FlinkSqlParserImpl.parseSqlStmtList(FlinkSqlParserImpl.java:306)
> at
> org.apache.calcite.sql.parser.SqlParser.parseStmtList(SqlParser.java:198)
> ... 33 more {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31380) Support enhanced show catalogs syntax
[ https://issues.apache.org/jira/browse/FLINK-31380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31380: --- 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. > Support enhanced show catalogs syntax > - > > Key: FLINK-31380 > URL: https://issues.apache.org/jira/browse/FLINK-31380 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / API, Table SQL / Planner >Reporter: Ran Tao >Assignee: Ran Tao >Priority: Major > Labels: pull-request-available, stale-assigned > > As FLIP discussed. We will support new syntax for some show operations. > To avoid bloat, this ticket supports ShowCatalogs. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31691) Add MAP_FROM_ENTRIES supported in SQL & Table API
[
https://issues.apache.org/jira/browse/FLINK-31691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31691:
---
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.
> Add MAP_FROM_ENTRIES supported in SQL & Table API
> -
>
> Key: FLINK-31691
> URL: https://issues.apache.org/jira/browse/FLINK-31691
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Affects Versions: 1.18.0
>Reporter: Jacky Lau
>Assignee: Jacky Lau
>Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.18.0
>
>
> map_from_entries(map) - Returns a map created from an arrays of row with two
> fields. Note that the number of fields in a row array should be 2 and the key
> of a row array should not be null.
> Syntax:
> map_from_entries(array_of_rows)
> Arguments:
> array_of_rows: an arrays of row with two fields.
> Returns:
> Returns a map created from an arrays of row with two fields. Note that the
> number of fields in a row array should be 2 and the key of a row array should
> not be null.
> Returns null if the argument is null
> {code:sql}
> > SELECT map_from_entries(map[1, 'a', 2, 'b']);
> [(1,"a"),(2,"b")]{code}
> See also
> presto [https://prestodb.io/docs/current/functions/map.html]
> spark https://spark.apache.org/docs/latest/api/sql/index.html#map_from_entries
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-32072) Create and wire FileMergingSnapshotManager with TaskManagerServices
[ https://issues.apache.org/jira/browse/FLINK-32072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-32072: --- 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. > Create and wire FileMergingSnapshotManager with TaskManagerServices > --- > > Key: FLINK-32072 > URL: https://issues.apache.org/jira/browse/FLINK-32072 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Checkpointing, Runtime / State Backends >Affects Versions: 1.18.0 >Reporter: Zakelly Lan >Assignee: Yanfei Lei >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30309) Add the ability to supply custom SslContexts for netty client/servers.
[ https://issues.apache.org/jira/browse/FLINK-30309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30309: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Add the ability to supply custom SslContexts for netty client/servers. > -- > > Key: FLINK-30309 > URL: https://issues.apache.org/jira/browse/FLINK-30309 > Project: Flink > Issue Type: Improvement > Components: Runtime / Network >Reporter: Steve Niemitz >Priority: Major > Labels: pull-request-available, stale-major > > The existing flink configuration supports on simple SSL configuration via > keystore/truststore configuration. For more advanced configuration options > it is desirable to be able to instead provide the entire pre-configured > SslContext, as well as all them to be reloaded if needed (eg, the certificate > material rotates while running). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30475) Improved speed of RocksDBMapState clear() using rocksDB.deleteRange
[
https://issues.apache.org/jira/browse/FLINK-30475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30475:
---
Labels: pull-request-available stale-major (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 issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Improved speed of RocksDBMapState clear() using rocksDB.deleteRange
> ---
>
> Key: FLINK-30475
> URL: https://issues.apache.org/jira/browse/FLINK-30475
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Affects Versions: 1.16.0
>Reporter: David Hrbacek
>Priority: Major
> Labels: pull-request-available, stale-major
>
> Currently {{RocksDBMapState#clear()}} is processed via keyRange traversing
> and inserting particular keys into BatchWrite for deletion.
> RocksDb offer much faster way how to delete key range - {{deleteRange}}
> This issue is follow-up for
> [FLINK-9070|https://issues.apache.org/jira/browse/FLINK-9070] where
> {{deleteRange}} was also considered. But at that time it implied slower read,
> it was buggy and not even available in the Java API of RocksDB. All of these
> problems were solved since that time (see also RocksDB [blog article for
> deleteRange|https://rocksdb.org/blog/2018/11/21/delete-range.html])
> Delete range enables to clear {{RocksDBMapState}} for one key in constant
> computational complexity whereas the old solution requires O(n ).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-27107) Typo in Task
[ https://issues.apache.org/jira/browse/FLINK-27107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-27107: --- Labels: pull-request-available stale-minor (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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Typo in Task > > > Key: FLINK-27107 > URL: https://issues.apache.org/jira/browse/FLINK-27107 > Project: Flink > Issue Type: Improvement > Components: Runtime / Task >Affects Versions: 1.15.0 >Reporter: dizhou cao >Priority: Minor > Labels: pull-request-available, stale-minor > > two small typos in Task > * TaskCancelerWatchDog/TaskInterrupter field: executerThread -> > executorThread > * TaskCanceler field: executer -> executor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26624) Running HA (hashmap, async) end-to-end test failed on azure due to unable to find master logs
[
https://issues.apache.org/jira/browse/FLINK-26624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26624:
---
Labels: stale-critical starter test-stability (was: starter test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> Running HA (hashmap, async) end-to-end test failed on azure due to unable to
> find master logs
> -
>
> Key: FLINK-26624
> URL: https://issues.apache.org/jira/browse/FLINK-26624
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.15.0, 1.17.0, 1.16.1
>Reporter: Yun Gao
>Priority: Critical
> Labels: stale-critical, starter, test-stability
> Attachments: 20230304.2-build-46800-flink-logs.tgz
>
>
> {code:java}
> Mar 12 04:31:15 Waiting for text Completed checkpoint [1-9]* for job
> 699ebf9bdcb51a9fe76db5463027d34c to appear 2 of times in logs...
> grep:
> /home/vsts/work/_temp/debug_files/flink-logs/*standalonesession-1*.log*: No
> such file or directory
> Mar 12 04:31:16 Starting standalonesession daemon on host fv-az302-918.
> grep:
> /home/vsts/work/_temp/debug_files/flink-logs/*standalonesession-1*.log*: No
> such file or directory
> Mar 12 04:41:23 A timeout occurred waiting for Completed checkpoint [1-9]*
> for job 699ebf9bdcb51a9fe76db5463027d34c to appear 2 of times in logs.
> Mar 12 04:41:23 Stopping job timeout watchdog (with pid=272045)
> Mar 12 04:41:23 Killing JM watchdog @ 273681
> Mar 12 04:41:23 Killing TM watchdog @ 274268
> Mar 12 04:41:23 [FAIL] Test script contains errors.
> Mar 12 04:41:23 Checking of logs skipped.
> Mar 12 04:41:23
> Mar 12 04:41:23 [FAIL] 'Running HA (hashmap, async) end-to-end test' failed
> after 10 minutes and 31 seconds! Test exited with exit code 1
> Mar 12 04:41:23
> 04:41:23 ##[group]Environment Information
> Mar 12 04:41:24 Searching for .dump, .dumpstream and related files in
> '/home/vsts/work/1/s'
> dmesg: read kernel buffer failed: Operation not permitted
> Mar 12 04:41:28 Stopping taskexecutor daemon (pid: 272837) on host
> fv-az302-918.
> Mar 12 04:41:29 Stopping standalonesession daemon (pid: 274590) on host
> fv-az302-918.
> Mar 12 04:41:35 Stopping zookeeper...
> Mar 12 04:41:36 Stopping zookeeper daemon (pid: 272248) on host fv-az302-918.
> The STDIO streams did not close within 10 seconds of the exit event from
> process '/usr/bin/bash'. This may indicate a child process inherited the
> STDIO streams and has not yet exited.
> ##[error]Bash exited with code '1'.
> {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=32945=logs=bea52777-eaf8-5663-8482-18fbc3630e81=b2642e3a-5b86-574d-4c8a-f7e2842bfb14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30218) [Kafka Connector] java.lang.OutOfMemoryError: Metaspace
[
https://issues.apache.org/jira/browse/FLINK-30218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30218:
---
Labels: bug stale-major (was: bug)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> [Kafka Connector] java.lang.OutOfMemoryError: Metaspace
> ---
>
> Key: FLINK-30218
> URL: https://issues.apache.org/jira/browse/FLINK-30218
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.15.1
> Environment: +*AWS EMR*+
> * Standard AWS EMR Cluster (1 master YARN node, 1 core node) - 2 vCore, 8 GB
> memory each
> * JDK 11 Coretto
> +*Kafka Consumer Config*+
> {code:java}
> acks = 1
> batch.size = 16384
> bootstrap.servers = [...]
> buffer.memory = 33554432
> client.dns.lookup = use_all_dns_ips
> client.id = producer-1
> compression.type = none
> connections.max.idle.ms = 54
> delivery.timeout.ms = 12
> enable.idempotence = false
> interceptor.classes = []
> internal.auto.downgrade.txn.commit = false
> key.serializer = class
> org.apache.kafka.common.serialization.ByteArraySerializer
> linger.ms = 0
> max.block.ms = 6
> max.in.flight.requests.per.connection = 5
> max.request.size = 1048576
> metadata.max.age.ms = 30
> metadata.max.idle.ms = 30
> metric.reporters = []
> metrics.num.samples = 2
> metrics.recording.level = INFO
> metrics.sample.window.ms = 3
> partitioner.class = class
> org.apache.kafka.clients.producer.internals.DefaultPartitioner
> receive.buffer.bytes = 32768
> reconnect.backoff.max.ms = 1000
> reconnect.backoff.ms = 50
> request.timeout.ms = 3
> retries = 2147483647
> retry.backoff.ms = 100
> sasl.client.callback.handler.class = class
> software.amazon.msk.auth.iam.IAMClientCallbackHandler
> sasl.jaas.config = [hidden]
> sasl.kerberos.kinit.cmd = /usr/bin/kinit
> sasl.kerberos.min.time.before.relogin = 6
> sasl.kerberos.service.name = null
> sasl.kerberos.ticket.renew.jitter = 0.05
> sasl.kerberos.ticket.renew.window.factor = 0.8
> sasl.login.callback.handler.class = null
> sasl.login.class = null
> sasl.login.refresh.buffer.seconds = 300
> sasl.login.refresh.min.period.seconds = 60
> sasl.login.refresh.window.factor = 0.8
> sasl.login.refresh.window.jitter = 0.05
> sasl.mechanism = AWS_MSK_IAM
> security.protocol = SASL_SSL
> security.providers = null
> send.buffer.bytes = 131072
> socket.connection.setup.timeout.max.ms = 3
> socket.connection.setup.timeout.ms = 1
> ssl.cipher.suites = null
> ssl.enabled.protocols = [TLSv1.2, TLSv1.3]
> ssl.endpoint.identification.algorithm = https
> ssl.engine.factory.class = null
> ssl.key.password = null
> ssl.keymanager.algorithm = SunX509
> ssl.keystore.certificate.chain = null
> ssl.keystore.key = null
> ssl.keystore.location = null
> ssl.keystore.password = null
> ssl.keystore.type = JKS
> ssl.protocol = TLSv1.3
> ssl.provider = null
> ssl.secure.random.implementation = null
> ssl.trustmanager.algorithm = PKIX
> ssl.truststore.certificates = null
> ssl.truststore.location = null
> ssl.truststore.password = null
> ssl.truststore.type = JKS
> transaction.timeout.ms = 360
> transactional.id = null
> value.serializer = class
> org.apache.kafka.common.serialization.ByteArraySerializer{code}
> +*Flink Config*+
> {code:java}
> taskmanager.memory.process.size=3g
> taskmanager.memory.jvm-metaspace.size=512m
> taskmanager.numberOfTaskSlots=2
> jobmanager.memory.process.size=3g
> jobmanager.memory.jvm-metaspace.size=256m
> jobmanager.web.address0.0.0.0
> env.java.opts.all-XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=${FLINK_LOG_PREFIX}.hprof {code}
>
>Reporter: Lukas Mahl
>Priority: Major
> Labels: bug, stale-major
> Attachments: dump.hprof.zip, image-2022-11-25-15-55-43-559.png
>
>
> Hello!
> I'm running a Flink application on AWS EMR which consumes from a Kafka Topic
> using the official Flink Kafka consumer. I'm running the application as a
> Flink batch job every 30 minutes and I see that the JobManager's metaspace is
> increasing every time I submit a new job and doesn't reduce once a job has
> finished
[jira] [Updated] (FLINK-29944) Support accumulator in source reader
[
https://issues.apache.org/jira/browse/FLINK-29944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29944:
---
Labels: pull-request-available stale-critical (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 issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> Support accumulator in source reader
>
>
> Key: FLINK-29944
> URL: https://issues.apache.org/jira/browse/FLINK-29944
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
>Affects Versions: 1.17.0
>Reporter: hk__lrzy
>Priority: Critical
> Labels: pull-request-available, stale-critical
>
> Source Reader is mainly for union batch and streaming logic in single
> interface, it's good point for the developer, but in the {{SourceFunction}}
> we can access {{runtimeconext}} to use accumulator before, now the
> {{SourceReaderContext}} have no method for it, this PR is mainly to support
> it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26839) SessionDispatcherLeaderProcessTest.recoverJobs_withJobIdRecoveryFailure_failsFatally failed on azures
[
https://issues.apache.org/jira/browse/FLINK-26839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26839:
---
Labels: auto-deprioritized-major stale-critical test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
>
> SessionDispatcherLeaderProcessTest.recoverJobs_withJobIdRecoveryFailure_failsFatally
> failed on azures
> --
>
> Key: FLINK-26839
> URL: https://issues.apache.org/jira/browse/FLINK-26839
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.15.0, 1.17.0
>Reporter: Yun Gao
>Priority: Critical
> Labels: auto-deprioritized-major, stale-critical, test-stability
>
> {code:java}
> Mar 24 04:11:15 [ERROR]
> SessionDispatcherLeaderProcessTest.recoverJobs_withJobIdRecoveryFailure_failsFatally:667->runJobRecoveryFailureTest:677
>
> Mar 24 04:11:15 Expecting
> Mar 24 04:11:15java.util.concurrent.CompletionException:
> org.apache.flink.util.FlinkRuntimeException: Could not retrieve job ids of
> persisted jobs.
> Mar 24 04:11:15 at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> Mar 24 04:11:15 at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> Mar 24 04:11:15 at
> java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:618)
> Mar 24 04:11:15 ...(5 remaining lines not displayed - this can be
> changed with Assertions.setMaxStackTraceElementsDisplayed)]>
> Mar 24 04:11:15 to be completed within 100L Millis.
> Mar 24 04:11:15
> Mar 24 04:11:15 exception caught while trying to get the future result:
> java.util.concurrent.TimeoutException
> Mar 24 04:11:15 at
> java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1784)
> Mar 24 04:11:15 at
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928)
> Mar 24 04:11:15 at
> org.assertj.core.internal.Futures.assertSucceededWithin(Futures.java:100)
> Mar 24 04:11:15 at
> org.assertj.core.api.AbstractCompletableFutureAssert.internalSucceedsWithin(AbstractCompletableFutureAssert.java:438)
> Mar 24 04:11:15 at
> org.assertj.core.api.AbstractCompletableFutureAssert.succeedsWithin(AbstractCompletableFutureAssert.java:434)
> Mar 24 04:11:15 at
> org.apache.flink.runtime.dispatcher.runner.SessionDispatcherLeaderProcessTest.runJobRecoveryFailureTest(SessionDispatcherLeaderProcessTest.java:677)
> Mar 24 04:11:15 at
> org.apache.flink.runtime.dispatcher.runner.SessionDispatcherLeaderProcessTest.recoverJobs_withJobIdRecoveryFailure_failsFatally(SessionDispatcherLeaderProcessTest.java:667)
> Mar 24 04:11:15 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> Mar 24 04:11:15 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Mar 24 04:11:15 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Mar 24 04:11:15 at java.lang.reflect.Method.invoke(Method.java:498)
> Mar 24 04:11:15 at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
> Mar 24 04:11:15 at
> org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
> Mar 24 04:11:15 at
>
[jira] [Updated] (FLINK-30479) Document flink-connector-files for local execution
[
https://issues.apache.org/jira/browse/FLINK-30479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30479:
---
Labels: pull-request-available stale-major (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 issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Document flink-connector-files for local execution
> --
>
> Key: FLINK-30479
> URL: https://issues.apache.org/jira/browse/FLINK-30479
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 1.16.0
>Reporter: Mingliang Liu
>Priority: Major
> Labels: pull-request-available, stale-major
>
> The file system SQL connector itself is included in Flink and does not
> require an additional dependency. However, if a user uses the filesystem
> connector for [local
> execution|https://nightlies.apache.org/flink/flink-docs-master/docs/dev/dataset/local_execution/#local-execution],
> for e.g. running Flink job in the IDE, she will need to add dependency.
> Otherwise, the user will get validation exception: {{{}Cannot discover a
> connector using option: 'connector'='filesystem'{}}}. This is confusing and
> can be documented.
> The scope of the files connector dependency should be {{{}provided{}}},
> because they should not be packaged into the JAR file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30242) Push localHashAggregate pass the union node
[ https://issues.apache.org/jira/browse/FLINK-30242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30242: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Push localHashAggregate pass the union node > --- > > Key: FLINK-30242 > URL: https://issues.apache.org/jira/browse/FLINK-30242 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Aitozi >Priority: Major > Labels: pull-request-available, stale-major > Attachments: screenshot-1.png, screenshot-2.png > > > The local hash aggregate after union will have an extra shuffle stage. We can > swap it with the union node so the local hash aggregate can chain with the > mapper stage saving the unnecessary shuffle, especially in the batch job. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30262) UpsertKafkaTableITCase failed when starting the container because waiting for a port timed out
[
https://issues.apache.org/jira/browse/FLINK-30262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30262:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> UpsertKafkaTableITCase failed when starting the container because waiting for
> a port timed out
> --
>
> Key: FLINK-30262
> URL: https://issues.apache.org/jira/browse/FLINK-30262
> Project: Flink
> Issue Type: Bug
> Components: Build System, Connectors / Kafka, Test Infrastructure
>Affects Versions: 1.16.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> {code:java}
> Dec 01 08:35:00 Caused by:
> org.testcontainers.containers.ContainerLaunchException: Timed out waiting for
> container port to open (172.17.0.1 ports: [60109, 60110] should be listening)
> Dec 01 08:35:00 at
> org.testcontainers.containers.wait.strategy.HostPortWaitStrategy.waitUntilReady(HostPortWaitStrategy.java:90)
> Dec 01 08:35:00 at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:51)
> Dec 01 08:35:00 at
> org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:926)
> Dec 01 08:35:00 at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:480)
> Dec 01 08:35:00 ... 33 more
> {code}
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43643=logs=aa18c3f6-13b8-5f58-86bb-c1cffb239496=502fb6c0-30a2-5e49-c5c2-a00fa3acb203=37366
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30196) Replace usage of deprecated Mockito's methods with advised by Mockito
[ https://issues.apache.org/jira/browse/FLINK-30196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30196: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Replace usage of deprecated Mockito's methods with advised by Mockito > - > > Key: FLINK-30196 > URL: https://issues.apache.org/jira/browse/FLINK-30196 > Project: Flink > Issue Type: Technical Debt > Components: Tests >Reporter: Sergey Nuyanzin >Priority: Major > Labels: pull-request-available, stale-major > > Currently there is a number of deprecated Mockito's methods in use. Most of > them will be removed in 4.* as stated at > https://github.com/mockito/mockito/releases/tag/v4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30163) StreamPandasUDFITTests.test_basic_functionality failed
[
https://issues.apache.org/jira/browse/FLINK-30163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30163:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> StreamPandasUDFITTests.test_basic_functionality failed
> --
>
> Key: FLINK-30163
> URL: https://issues.apache.org/jira/browse/FLINK-30163
> Project: Flink
> Issue Type: Bug
> Components: API / Python
>Affects Versions: 1.15.2
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> [This
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42956=logs=bf5e383b-9fd3-5f02-ca1c-8f788e2e76d3=85189c57-d8a0-5c9c-b61d-fc05cfac62cf=26331]
> failed due to {{StreamPandasUDFITTests.test_basic_functionality}}
> {code:java}
> ov 09 01:49:14 ___
> StreamPandasUDFITTests.test_basic_functionality
> Nov 09 01:49:14
> Nov 09 01:49:14 self =
> testMethod=test_basic_functionality>
> Nov 09 01:49:14
> Nov 09 01:49:14 def test_basic_functionality(self):
> Nov 09 01:49:14 # pandas UDF
> Nov 09 01:49:14 add_one = udf(lambda i: i + 1,
> result_type=DataTypes.BIGINT(), func_type="pandas")
> Nov 09 01:49:14
> Nov 09 01:49:14 # general Python UDF
> Nov 09 01:49:14 subtract_one = udf(SubtractOne(), DataTypes.BIGINT(),
> DataTypes.BIGINT())
> Nov 09 01:49:14
> Nov 09 01:49:14 table_sink = source_sink_utils.TestAppendSink(
> Nov 09 01:49:14 ['a', 'b', 'c', 'd'],
> Nov 09 01:49:14 [DataTypes.BIGINT(), DataTypes.BIGINT(),
> DataTypes.BIGINT(), DataTypes.BIGINT()])
> Nov 09 01:49:14 self.t_env.register_table_sink("Results", table_sink)
> Nov 09 01:49:14
> Nov 09 01:49:14 t = self.t_env.from_elements([(1, 2, 3), (2, 5, 6),
> (3, 1, 9)], ['a', 'b', 'c'])
> Nov 09 01:49:14 t.where(add_one(t.b) <= 3) \
> Nov 09 01:49:14 .select(t.a, t.b + 1, add(t.a + 1,
> subtract_one(t.c)) + 2, add(add_one(t.a), 1)) \
> Nov 09 01:49:14 > .execute_insert("Results") \
> Nov 09 01:49:14 .wait()
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30300) Building wheels on macos took longer than expected
[
https://issues.apache.org/jira/browse/FLINK-30300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30300:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Building wheels on macos took longer than expected
> --
>
> Key: FLINK-30300
> URL: https://issues.apache.org/jira/browse/FLINK-30300
> Project: Flink
> Issue Type: Bug
> Components: API / Python, Build System / Azure Pipelines, Test
> Infrastructure
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> Looks like {{build_wheels_on_macos}} reached the Azure-specific limit of 1h
> runtime for this job:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43700=logs=f73b5736-8355-5390-ec71-4dfdec0ce6c5=90f7230e-bf5a-531b-8566-ad48d3e03bbb=176
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30302) WatermarkAssignerChangelogNormalizeTransposeRuleTest failed
[
https://issues.apache.org/jira/browse/FLINK-30302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30302:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> WatermarkAssignerChangelogNormalizeTransposeRuleTest failed
> ---
>
> Key: FLINK-30302
> URL: https://issues.apache.org/jira/browse/FLINK-30302
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43715=logs=0c940707-2659-5648-cbe6-a1ad63045f0a=075c2716-8010-5565-fe08-3c4bb45824a4=11792
> {code}
> Dec 05 04:26:28 [ERROR]
> org.apache.flink.table.planner.plan.rules.physical.stream.WatermarkAssignerChangelogNormalizeTransposeRuleTest.testPushdownCalcNotAffectChangelogNormalizeKey
> Time elapsed: 0.601 s <<< FAILURE!
> Dec 05 04:26:28 org.junit.ComparisonFailure:
> Dec 05 04:26:28 optimized rel plan expected:<...c(select=[a, b, f],
> [changelogMode=[I])
> Dec 05 04:26:28 +- TemporalJoin(joinType=[InnerJoin], where=[AND(=(a, a0),
> __TEMPORAL_JOIN_CONDITION(ingestion_time, ingestion_time0,
> __TEMPORAL_JOIN_CONDITION_PRIMARY_KEY(a0), __TEMPORAL_JOIN_LEFT_KEY(a),
> __TEMPORAL_JOIN_RIGHT_KEY(a0)))], select=[ingestion_time, a, b,
> ingestion_time0, a0, f], changelogMode=[I])
> Dec 05 04:26:28:- Exchange(distribution=[hash[a]], changelogMode=[I])
> Dec 05 04:26:28: +- WatermarkAssigner(rowtime=[ingestion_time],
> watermark=[ingestion_time], changelogMode=[I])
> Dec 05 04:26:28: +- Calc(select=[CAST(ingestion_time AS TIMESTAMP(3)
> *ROWTIME*) AS ingestion_time, a, b], changelogMode=[I])
> Dec 05 04:26:28:+- TableSourceScan(table=[[default_catalog,
> default_database, t1]], fields=[a, b, ingestion_time], changelogMode=[I])
> Dec 05 04:26:28+- Exchange(distribution=[hash[a]],
> changelogMode=[I,UB,UA,D])
> Dec 05 04:26:28 +- Calc(select=[ingestion_time, a, f], where=[f],
> changelogMode=[I,UB,UA,D])
> Dec 05 04:26:28 +- ChangelogNormalize(key=[a],
> changelogMode=[I,UB,UA,D])
> Dec 05 04:26:28 +- Exchange(distribution=[hash[a]],
> changelogMode=[I,UA,D])
> Dec 05 04:26:28+- WatermarkAssigner(rowtime=[ingestion_time],
> watermark=[ingestion_time], changelogMode=[I,UA,D])
> Dec 05 04:26:28 +- Calc(select=[CAST(ingestion_time AS
> TIMESTAMP(3) *ROWTIME*) AS ingestion_time, a, f], changelogMode=[I,UA,D])
> Dec 05 04:26:28] +-...> but was:<...c(select=[a, b, f],
> [where=[f], changelogMode=[I])
> Dec 05 04:26:28 +- TemporalJoin(joinType=[InnerJoin], where=[AND(=(a, a0),
> __TEMPORAL_JOIN_CONDITION(ingestion_time, ingestion_time0,
> __TEMPORAL_JOIN_CONDITION_PRIMARY_KEY(a0), __TEMPORAL_JOIN_LEFT_KEY(a),
> __TEMPORAL_JOIN_RIGHT_KEY(a0)))], select=[ingestion_time, a, b,
> ingestion_time0, a0, f], changelogMode=[I])
> Dec 05 04:26:28:- Exchange(distribution=[hash[a]], changelogMode=[I])
> Dec 05 04:26:28: +- WatermarkAssigner(rowtime=[ingestion_time],
> watermark=[ingestion_time], changelogMode=[I])
> Dec 05 04:26:28: +- Calc(select=[CAST(ingestion_time AS TIMESTAMP(3)
> *ROWTIME*) AS ingestion_time, a, b], changelogMode=[I])
> Dec 05 04:26:28:+- TableSourceScan(table=[[default_catalog,
> default_database, t1]], fields=[a, b, ingestion_time], changelogMode=[I])
> Dec 05 04:26:28+- Exchange(distribution=[hash[a]], changelogMode=[I,UA,D])
> Dec 05 04:26:28 +- ChangelogNormalize(key=[a], changelogMode=[I,UA,D])
> Dec 05 04:26:28 +- Exchange(distribution=[hash[a]],
> changelogMode=[I,UA,D])
> Dec 05 04:26:28 +- WatermarkAssigner(rowtime=[ingestion_time],
> watermark=[ingestion_time], changelogMode=[I,UA,D])
> Dec 05 04:26:28+- Calc(select=[CAST(ingestion_time AS
> TIMESTAMP(3) *ROWTIME*) AS ingestion_time, a, f], changelogMode=[I,UA,D])
> Dec 05 04:26:28 ] +-...>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26625) KinesisFirehoseSinkITCase failed on azure due to Could not find a valid Docker environment
[
https://issues.apache.org/jira/browse/FLINK-26625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26625:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> KinesisFirehoseSinkITCase failed on azure due to Could not find a valid
> Docker environment
> --
>
> Key: FLINK-26625
> URL: https://issues.apache.org/jira/browse/FLINK-26625
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines
>Affects Versions: 1.15.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> Mar 12 03:04:48 [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0,
> Time elapsed: 11.946 s <<< FAILURE! - in
> org.apache.flink.connector.firehose.sink.KinesisFirehoseSinkITCase
> Mar 12 03:04:48 [ERROR]
> org.apache.flink.connector.firehose.sink.KinesisFirehoseSinkITCase Time
> elapsed: 11.946 s <<< ERROR!
> Mar 12 03:04:48 java.lang.IllegalStateException: Could not find a valid
> Docker environment. Please see logs and check configuration
> Mar 12 03:04:48 at
> org.testcontainers.dockerclient.DockerClientProviderStrategy.lambda$getFirstValidStrategy$4(DockerClientProviderStrategy.java:156)
> Mar 12 03:04:48 at java.util.Optional.orElseThrow(Optional.java:290)
> Mar 12 03:04:48 at
> org.testcontainers.dockerclient.DockerClientProviderStrategy.getFirstValidStrategy(DockerClientProviderStrategy.java:148)
> Mar 12 03:04:48 at
> org.testcontainers.DockerClientFactory.getOrInitializeStrategy(DockerClientFactory.java:146)
> Mar 12 03:04:48 at
> org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:188)
> Mar 12 03:04:48 at
> org.testcontainers.DockerClientFactory$1.getDockerClient(DockerClientFactory.java:101)
> Mar 12 03:04:48 at
> com.github.dockerjava.api.DockerClientDelegate.authConfig(DockerClientDelegate.java:107)
> Mar 12 03:04:48 at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:316)
> Mar 12 03:04:48 at
> org.testcontainers.containers.GenericContainer.starting(GenericContainer.java:1066)
> Mar 12 03:04:48 at
> org.testcontainers.containers.FailureDetectingExternalResource$1.evaluate(FailureDetectingExternalResource.java:29)
> Mar 12 03:04:48 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> Mar 12 03:04:48 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Mar 12 03:04:48 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> Mar 12 03:04:48 at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> Mar 12 03:04:48 at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> Mar 12 03:04:48 at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
> Mar 12 03:04:48 at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> Mar 12 03:04:48 at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:107)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:114)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:86)
> Mar 12 03:04:48 at
> org.junit.platform.launcher.core.DefaultLauncherSession$DelegatingLauncher.execute(DefaultLauncherSession.java:86)
> Mar 12 03:04:48 at
>
[jira] [Updated] (FLINK-31511) Translate documentation sql_functions_zh.yml to the latest version
[ https://issues.apache.org/jira/browse/FLINK-31511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31511: --- 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. > Translate documentation sql_functions_zh.yml to the latest version > --- > > Key: FLINK-31511 > URL: https://issues.apache.org/jira/browse/FLINK-31511 > Project: Flink > Issue Type: Improvement > Components: Documentation, Table SQL / API >Affects Versions: 1.17.0 >Reporter: Hang Ruan >Assignee: Hang Ruan >Priority: Minor > Labels: pull-request-available, stale-assigned > Fix For: 1.18.0, 1.17.2 > > > Some content of these functions in sql_functions_zh.yml is outdated. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30488) OpenSearch implementation of Async Sink
[ https://issues.apache.org/jira/browse/FLINK-30488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30488: --- Labels: pull-request-available stale-major (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 issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > OpenSearch implementation of Async Sink > --- > > Key: FLINK-30488 > URL: https://issues.apache.org/jira/browse/FLINK-30488 > Project: Flink > Issue Type: New Feature > Components: Connectors / Opensearch >Affects Versions: opensearch-1.0.0 >Reporter: Andriy Redko >Priority: Major > Labels: pull-request-available, stale-major > > The current OpenSearch connector only uses the SinkFunction. > * Implement an asynchronous sink (Async Sink) support for OpenSearch > connector > * Update documentation > * Add end to end tests > More details to be found > [https://cwiki.apache.org/confluence/display/FLINK/FLIP-171%3A+Async+Sink] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29926) File source continuous monitoring mode ignoring files during savepoint upgrade mode
[
https://issues.apache.org/jira/browse/FLINK-29926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29926:
---
Labels: 1.15 Flink ReadFile stale-critical (was: 1.15 Flink ReadFile)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> File source continuous monitoring mode ignoring files during savepoint
> upgrade mode
> ---
>
> Key: FLINK-29926
> URL: https://issues.apache.org/jira/browse/FLINK-29926
> Project: Flink
> Issue Type: Bug
>Reporter: Avinash
>Priority: Critical
> Labels: 1.15, Flink, ReadFile, stale-critical
>
> During a stateful application upgrade using flink kubernetes operator, the
> StreamExecutionEnvironment.readFile() with
> FileProcessingMode.PROCESS_CONTINUOUSLY mode operator fails to detect any new
> changes that has happened on the same file in the directory.
>
> *Background* : Currently we have a fresh deployment of the application using
> kuberenetes operator using savepoint as the upgarde mode and checkpoint
> enabled.
> env.readFile() with FileProcessingMode.PROCESS_CONTINUOUSLY mode operator
> starts continuosly monitoring the directory (S3 prefix) for any changes and
> also checkpoints for the provided duration.
> {noformat}
> 2022-11-07 10:47:13.577 UTC taskmanager-1-1 [priority='DEBUG' thread='Source:
> Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - Opened ContinuousFileMonitoringFunction (taskIdx= 0) for path:
> s3://test-app/configs
> ...
> ...
> 2022-11-07 10:47:13.996 UTC taskmanager-1-1 [priority='DEBUG' thread='Legacy
> Source Thread - Source: Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - Ignoring s3://test-app/configs/control-event-config.json, with mod time=
> 1667817365000 and global mod time= 1667817365000
> ...
> ...
> 2022-11-07 10:51:40.896 UTC taskmanager-1-1 [priority='DEBUG' thread='Source:
> Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - ContinuousFileMonitoringFunction checkpointed 1667817365000.{noformat}
> Now we try to upgrade the application using the kubernetes operator, due to
> this the application tries to take savepoint by using the below Suspend
> Mechanism - Cancel with savepoint.
> By doing this, the application calls the cancel methods which inturn sets the
> globalModificationTime = Long.MAX_VALUE and then the savepoint is taken.
> {noformat}
> 2022-11-07 10:54:12.897 UTC taskmanager-1-1 [priority='DEBUG' thread='Legacy
> Source Thread - Source: Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - Ignoring s3://test-app/configs/control-event-config.json, with mod time=
> 1667817365000 and global mod time= 1667817365000
> ...
> 2022-11-07 10:55:12.899 UTC taskmanager-1-1 [priority='DEBUG' thread='Source:
> Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - ContinuousFileMonitoringFunction checkpointed 9223372036854775807
>
> 2022-11-07 10:55:13.090 UTC taskmanager-1-1 [priority='DEBUG' thread='Source:
> Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - Closed File Monitoring Source for path: s3://test-app/{noformat}
> Due to this, the globalModificationTime changed from 1667817365000 to
> MAX_VALUE (9223372036854775807) and gets stored in the savepoint state.
> Once the application restarts with the new changes, the env.readFile()
> operator restores the previous state in which the globalModificationTime =
> Long.MAX_VALUE and starts ignoring any changes done to the file after upgrade
> {noformat}
> 2022-11-07 11:00:13.577 UTC taskmanager-1-1 [priority='INFO' thread='Source:
> Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - Restoring state for the ContinuousFileMonitoringFunction
>
> 2022-11-07 11:00:13.577 UTC taskmanager-1-1 [priority='DEBUG' thread='Source:
> Custom File Source (1/1)#0']
> org.apache.flink.streaming.api.functions.source.ContinuousFileMonitoringFunction@
> - ContinuousFileMonitoringFunction retrieved a global mod time of
>
[jira] [Updated] (FLINK-26402) MinioTestContainerTest.testS3EndpointNeedsToBeSpecifiedBeforeInitializingFileSyste failed due to Container startup failed
[
https://issues.apache.org/jira/browse/FLINK-26402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26402:
---
Labels: auto-deprioritized-critical pull-request-available stale-critical
test-stability (was: auto-deprioritized-critical pull-request-available
test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> MinioTestContainerTest.testS3EndpointNeedsToBeSpecifiedBeforeInitializingFileSyste
> failed due to Container startup failed
> -
>
> Key: FLINK-26402
> URL: https://issues.apache.org/jira/browse/FLINK-26402
> Project: Flink
> Issue Type: Bug
> Components: FileSystems
>Affects Versions: 1.15.0, 1.16.0, 1.17.0
>Reporter: Yun Gao
>Priority: Critical
> Labels: auto-deprioritized-critical, pull-request-available,
> stale-critical, test-stability
>
> {code:java}
> 2022-02-24T02:49:59.3646340Z Feb 24 02:49:59 [ERROR] Tests run: 6, Failures:
> 0, Errors: 1, Skipped: 0, Time elapsed: 49.457 s <<< FAILURE! - in
> org.apache.flink.fs.s3.common.MinioTestContainerTest
> 2022-02-24T02:49:59.3648027Z Feb 24 02:49:59 [ERROR]
> org.apache.flink.fs.s3.common.MinioTestContainerTest.testS3EndpointNeedsToBeSpecifiedBeforeInitializingFileSyste
> Time elapsed: 5.751 s <<< ERROR!
> 2022-02-24T02:49:59.3648805Z Feb 24 02:49:59
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed
> 2022-02-24T02:49:59.3651640Z Feb 24 02:49:59 at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:336)
> 2022-02-24T02:49:59.3652820Z Feb 24 02:49:59 at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
> 2022-02-24T02:49:59.3653619Z Feb 24 02:49:59 at
> org.apache.flink.core.testutils.TestContainerExtension.instantiateTestContainer(TestContainerExtension.java:59)
> 2022-02-24T02:49:59.3654319Z Feb 24 02:49:59 at
> org.apache.flink.core.testutils.TestContainerExtension.before(TestContainerExtension.java:70)
> 2022-02-24T02:49:59.3655057Z Feb 24 02:49:59 at
> org.apache.flink.core.testutils.EachCallbackWrapper.beforeEach(EachCallbackWrapper.java:45)
> 2022-02-24T02:49:59.3656153Z Feb 24 02:49:59 at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeEachCallbacks$2(TestMethodTestDescriptor.java:163)
> 2022-02-24T02:49:59.3657088Z Feb 24 02:49:59 at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$6(TestMethodTestDescriptor.java:199)
> 2022-02-24T02:49:59.3657905Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> 2022-02-24T02:49:59.3659016Z Feb 24 02:49:59 at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:199)
> 2022-02-24T02:49:59.3660004Z Feb 24 02:49:59 at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeEachCallbacks(TestMethodTestDescriptor.java:162)
> 2022-02-24T02:49:59.3660997Z Feb 24 02:49:59 at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:129)
> 2022-02-24T02:49:59.3662153Z Feb 24 02:49:59 at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:66)
> 2022-02-24T02:49:59.3663189Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
> 2022-02-24T02:49:59.3664211Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> 2022-02-24T02:49:59.3664971Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
> 2022-02-24T02:49:59.3665623Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> 2022-02-24T02:49:59.3666433Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
> 2022-02-24T02:49:59.3667322Z Feb 24 02:49:59 at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
>
[jira] [Updated] (FLINK-26569) testResumeWithWrongOffset(org.apache.flink.runtime.fs.hdfs.HadoopRecoverableWriterTest) failing
[
https://issues.apache.org/jira/browse/FLINK-26569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26569:
---
Labels: auto-deprioritized-critical auto-deprioritized-major stale-minor
test-stability (was: auto-deprioritized-critical auto-deprioritized-major
test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> testResumeWithWrongOffset(org.apache.flink.runtime.fs.hdfs.HadoopRecoverableWriterTest)
> failing
> ---
>
> Key: FLINK-26569
> URL: https://issues.apache.org/jira/browse/FLINK-26569
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem, Connectors / Hadoop
> Compatibility
>Affects Versions: 1.13.6, 1.15.0
>Reporter: Matthias Pohl
>Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> stale-minor, test-stability
>
> There's a test failure in [this
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=32792=logs=ba53eb01-1462-56a3-8e98-0dd97fbcaab5=bfbc6239-57a0-5db0-63f3-41551b4f7d51=10107]
> due to {{HadoopRecoverableWriterTest.testResumeWithWrongOffset}}:
> {code}
> Mar 10 00:46:04 [ERROR]
> testResumeWithWrongOffset(org.apache.flink.runtime.fs.hdfs.HadoopRecoverableWriterTest)
> Time elapsed: 100.39 s <<< FAILURE!
> Mar 10 00:46:04 java.lang.AssertionError
> Mar 10 00:46:04 at org.junit.Assert.fail(Assert.java:86)
> Mar 10 00:46:04 at org.junit.Assert.fail(Assert.java:95)
> Mar 10 00:46:04 at
> org.apache.flink.core.fs.AbstractRecoverableWriterTest.testResumeWithWrongOffset(AbstractRecoverableWriterTest.java:381)
> Mar 10 00:46:04 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> Mar 10 00:46:04 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Mar 10 00:46:04 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Mar 10 00:46:04 at java.lang.reflect.Method.invoke(Method.java:498)
> Mar 10 00:46:04 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> Mar 10 00:46:04 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> Mar 10 00:46:04 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> Mar 10 00:46:04 at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> Mar 10 00:46:04 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> Mar 10 00:46:04 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> Mar 10 00:46:04 at
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> Mar 10 00:46:04 at
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> Mar 10 00:46:04 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> Mar 10 00:46:04 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> Mar 10 00:46:04 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> Mar 10 00:46:04 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> Mar 10 00:46:04 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> Mar 10 00:46:04 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> Mar 10 00:46:04 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> Mar 10 00:46:04 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> Mar 10 00:46:04 at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> Mar 10 00:46:04
[jira] [Updated] (FLINK-29671) Kubernetes e2e test fails during test initialization
[
https://issues.apache.org/jira/browse/FLINK-29671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29671:
---
Labels: stale-critical starter test-stability (was: starter test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> Kubernetes e2e test fails during test initialization
>
>
> Key: FLINK-29671
> URL: https://issues.apache.org/jira/browse/FLINK-29671
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes, Test Infrastructure
>Affects Versions: 1.16.0, 1.17.0, 1.15.3
>Reporter: Matthias Pohl
>Priority: Critical
> Labels: stale-critical, starter, test-stability
> Attachments: kubernetes_test_failure.log
>
>
> There are two build failures ([branch based on
> release-1.16|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42038=logs=bea52777-eaf8-5663-8482-18fbc3630e81=b2642e3a-5b86-574d-4c8a-f7e2842bfb14=5377]
> and [a release-1.15
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42073=logs=bea52777-eaf8-5663-8482-18fbc3630e81=b2642e3a-5b86-574d-4c8a-f7e2842bfb14=4684])
> that are (not exclusively) caused by the e2e test {{Kubernetes test}}
> failing in the initialization phase (i.e. when installing all artifacts):
> See the attached logs from the {{release-1.15}} build's CI output. No logs
> are present as artifacts.
> *UPDATE*: The error we're seeing is actually FLINK-28269 because we failed to
> download {{crictl}}. Looks like we reached some download limit:
> {code}
> 2022-10-16T05:58:33.0821044Z --2022-10-16 05:58:33--
> https://objects.githubusercontent.com/github-production-release-asset-2e65be/80172100/7186c302-3766-4ed5-920a-f85c9d6334ac?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAIWNJYAX4CSVEH53A%2F20221016%2Fus-east-1%2Fs3%2Faws4
> _request=20221016T055833Z=300=5c24f88d9891e793000a904879be5e8913d643cbff1bfdfb8d0cf3c6e7a7908b=host_id=0_id=0_id=80172100=attachment%3B%20filename%3Dcrictl-v1.24.2-linux-amd64.t
> ar.gz=application%2Foctet-stream
> 2022-10-16T05:58:33.1021704Z Resolving objects.githubusercontent.com
> (objects.githubusercontent.com)... 185.199.108.133, 185.199.111.133,
> 185.199.110.133, ...
> 2022-10-16T05:58:33.1128247Z Connecting to objects.githubusercontent.com
> (objects.githubusercontent.com)|185.199.108.133|:443... connected.
> 2022-10-16T05:58:38.5605126Z HTTP request sent, awaiting response... 503
> Egress is over the account limit.
> 2022-10-16T05:58:38.5606342Z 2022-10-16 05:58:38 ERROR 503: Egress is over
> the account limit..
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-28076) StreamFaultToleranceTestBase runs into timeout
[
https://issues.apache.org/jira/browse/FLINK-28076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28076:
---
Labels: stale-critical test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> StreamFaultToleranceTestBase runs into timeout
> --
>
> Key: FLINK-28076
> URL: https://issues.apache.org/jira/browse/FLINK-28076
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
>Affects Versions: 1.16.0, 1.17.0
>Reporter: Matthias Pohl
>Priority: Critical
> Labels: stale-critical, test-stability
>
> [Build
> #36259|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36259=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=86f654fa-ab48-5c1a-25f4-7e7f6afb9bba=12054]
> got stuck in a {{StreamFaultToleranceTestBase}} subclass:
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7eff8c00b800 nid=0xf1a waiting on
> condition [0x7eff92eca000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x82213498> (a
> java.util.concurrent.CompletableFuture$Signaller)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1707)
> at
> java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3323)
> at
> java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1742)
> at
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
> at
> org.apache.flink.test.util.TestUtils.submitJobAndWaitForResult(TestUtils.java:92)
> at
> org.apache.flink.test.checkpointing.StreamFaultToleranceTestBase.runCheckpointedProgram(StreamFaultToleranceTestBase.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> [...]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-27285) CassandraConnectorITCase failed on azure due to NoHostAvailableException
[
https://issues.apache.org/jira/browse/FLINK-27285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-27285:
---
Labels: auto-deprioritized-major stale-critical test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> CassandraConnectorITCase failed on azure due to NoHostAvailableException
>
>
> Key: FLINK-27285
> URL: https://issues.apache.org/jira/browse/FLINK-27285
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Cassandra
>Affects Versions: 1.16.0, 1.15.3, cassandra-3.0.0
>Reporter: Yun Gao
>Priority: Critical
> Labels: auto-deprioritized-major, stale-critical, test-stability
>
> {code:java}
> 2022-04-17T06:24:40.1216092Z Apr 17 06:24:40 [ERROR]
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorITCase
> Time elapsed: 29.81 s <<< ERROR!
> 2022-04-17T06:24:40.1218517Z Apr 17 06:24:40
> com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s)
> tried for query failed (tried: /172.17.0.1:53053
> (com.datastax.driver.core.exceptions.OperationTimedOutException:
> [/172.17.0.1] Timed out waiting for server response))
> 2022-04-17T06:24:40.1220821Z Apr 17 06:24:40 at
> com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:84)
> 2022-04-17T06:24:40.1222816Z Apr 17 06:24:40 at
> com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:37)
> 2022-04-17T06:24:40.1224696Z Apr 17 06:24:40 at
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
> 2022-04-17T06:24:40.1226624Z Apr 17 06:24:40 at
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
> 2022-04-17T06:24:40.1228346Z Apr 17 06:24:40 at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:63)
> 2022-04-17T06:24:40.1229839Z Apr 17 06:24:40 at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:39)
> 2022-04-17T06:24:40.1231736Z Apr 17 06:24:40 at
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorITCase.startAndInitializeCassandra(CassandraConnectorITCase.java:385)
> 2022-04-17T06:24:40.1233614Z Apr 17 06:24:40 at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2022-04-17T06:24:40.1234992Z Apr 17 06:24:40 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 2022-04-17T06:24:40.1236194Z Apr 17 06:24:40 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 2022-04-17T06:24:40.1237598Z Apr 17 06:24:40 at
> java.lang.reflect.Method.invoke(Method.java:498)
> 2022-04-17T06:24:40.1238768Z Apr 17 06:24:40 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> 2022-04-17T06:24:40.1240056Z Apr 17 06:24:40 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 2022-04-17T06:24:40.1242109Z Apr 17 06:24:40 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> 2022-04-17T06:24:40.1243493Z Apr 17 06:24:40 at
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> 2022-04-17T06:24:40.1244903Z Apr 17 06:24:40 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> 2022-04-17T06:24:40.1246352Z Apr 17 06:24:40 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> 2022-04-17T06:24:40.1247809Z Apr 17 06:24:40 at
> org.testcontainers.containers.FailureDetectingExternalResource$1.evaluate(FailureDetectingExternalResource.java:30)
> 2022-04-17T06:24:40.1249193Z Apr 17 06:24:40 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> 2022-04-17T06:24:40.1250395Z Apr 17 06:24:40 at
> org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 2022-04-17T06:24:40.1251468Z Apr 17 06:24:40 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 2022-04-17T06:24:40.1252601Z Apr 17 06:24:40 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> 2022-04-17T06:24:40.1253640Z Apr 17 06:24:40 at
> org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> 2022-04-17T06:24:40.1254768Z Apr 17 06:24:40 at
>
[jira] [Updated] (FLINK-28321) HiveDialectQueryITCase fails with error code 137
[
https://issues.apache.org/jira/browse/FLINK-28321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28321:
---
Labels: stale-critical stale-major test-stability (was: stale-major
test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> HiveDialectQueryITCase fails with error code 137
>
>
> Key: FLINK-28321
> URL: https://issues.apache.org/jira/browse/FLINK-28321
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Hive
>Affects Versions: 1.15.0, 1.17.0
>Reporter: Martijn Visser
>Priority: Critical
> Labels: stale-critical, stale-major, test-stability
>
> {code:java}
> Moving data to directory
> file:/tmp/junit6349996144152770842/warehouse/db1.db/src1/.hive-staging_hive_2022-06-30_03-47-28_878_1781340705558822791-1/-ext-1
> Loading data to table db1.src1
> MapReduce Jobs Launched:
> Stage-Stage-1: HDFS Read: 0 HDFS Write: 0 SUCCESS
> Total MapReduce CPU Time Spent: 0 msec
> OK
> OK
> OK
> OK
> OK
> OK
> OK
> OK
> OK
> OK
> OK
> OK
> ##[error]Exit code 137 returned from process: file name '/bin/docker',
> arguments 'exec -i -u 1001 -w /home/agent02_azpcontainer
> 8f23cd917ec9d96c13789dabcaafe59398053d00ecf042a5426f9d1588ade349
> /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.
> {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=37387=logs=fc5181b0-e452-5c8f-68de-1097947f6483=995c650b-6573-581c-9ce6-7ad4cc038461=24786
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30108) ZooKeeperLeaderElectionConnectionHandlingTest.testLoseLeadershipOnLostConnectionIfTolerateSuspendedConnectionsIsEnabled times out
[
https://issues.apache.org/jira/browse/FLINK-30108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30108:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> ZooKeeperLeaderElectionConnectionHandlingTest.testLoseLeadershipOnLostConnectionIfTolerateSuspendedConnectionsIsEnabled
> times out
> -
>
> Key: FLINK-30108
> URL: https://issues.apache.org/jira/browse/FLINK-30108
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Tests
>Affects Versions: 1.17.0
>Reporter: Leonard Xu
>Priority: Major
> Labels: stale-major, test-stability
> Attachments: FLINK-30108.tar.gz, zookeeper-server.FLINK-30108.log
>
>
> {noformat}
> Nov 18 01:02:58 [INFO] Tests run: 16, Failures: 0, Errors: 0, Skipped: 0,
> Time elapsed: 109.22 s - in
> org.apache.flink.runtime.operators.hash.InPlaceMutableHashTableTest
> Nov 18 01:18:09
> ==
> Nov 18 01:18:09 Process produced no output for 900 seconds.
> Nov 18 01:18:09
> ==
> Nov 18 01:18:09
> ==
> Nov 18 01:18:09 The following Java processes are running (JPS)
> Nov 18 01:18:09
> ==
> Picked up JAVA_TOOL_OPTIONS: -XX:+HeapDumpOnOutOfMemoryError
> Nov 18 01:18:09 924 Launcher
> Nov 18 01:18:09 23421 surefirebooter1178962604207099497.jar
> Nov 18 01:18:09 11885 Jps
> Nov 18 01:18:09
> ==
> Nov 18 01:18:09 Printing stack trace of Java process 924
> Nov 18 01:18:09
> ==
> Picked up JAVA_TOOL_OPTIONS: -XX:+HeapDumpOnOutOfMemoryError
> Nov 18 01:18:09 2022-11-18 01:18:09
> Nov 18 01:18:09 Full thread dump OpenJDK 64-Bit Server VM (25.292-b10 mixed
> mode):
> ...
> ...
> ...
> Nov 18 01:18:09
> ==
> Nov 18 01:18:09 Printing stack trace of Java process 11885
> Nov 18 01:18:09
> ==
> 11885: No such process
> Nov 18 01:18:09 Killing process with pid=923 and all descendants
> /__w/2/s/tools/ci/watchdog.sh: line 113: 923 Terminated $cmd
> Nov 18 01:18:10 Process exited with EXIT CODE: 143.
> Nov 18 01:18:10 Trying to KILL watchdog (919).
> Nov 18 01:18:10 Searching for .dump, .dumpstream and related files in
> '/__w/2/s'
> Nov 18 01:18:16 Moving
> '/__w/2/s/flink-runtime/target/surefire-reports/2022-11-18T00-55-55_041-jvmRun3.dumpstream'
> to target directory ('/__w/_temp/debug_files')
> Nov 18 01:18:16 Moving
> '/__w/2/s/flink-runtime/target/surefire-reports/2022-11-18T00-55-55_041-jvmRun3.dump'
> to target directory ('/__w/_temp/debug_files')
> The STDIO streams did not close within 10 seconds of the exit event from
> process '/bin/bash'. This may indicate a child process inherited the STDIO
> streams and has not yet exited.
> ##[error]Bash exited with code '143'.
> Finishing: Test - core
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43277=logs=0e7be18f-84f2-53f0-a32d-4a5e4a174679=7c1d86e3-35bd-5fd5-3b7c-30c126a78702
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30136) ElasticsearchSinkITCase.testElasticsearchSink failed on azure due to ES service unavailable
[
https://issues.apache.org/jira/browse/FLINK-30136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30136:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> ElasticsearchSinkITCase.testElasticsearchSink failed on azure due to ES
> service unavailable
> ---
>
> Key: FLINK-30136
> URL: https://issues.apache.org/jira/browse/FLINK-30136
> Project: Flink
> Issue Type: Bug
> Components: Connectors / ElasticSearch
>Affects Versions: 1.16.0, elasticsearch-3.0.0
>Reporter: Leonard Xu
>Priority: Major
> Labels: stale-major, test-stability
>
> {noformat}
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:177)
> Nov 22 02:24:55 at
> org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:436)
> Nov 22 02:24:55 at
> org.apache.http.nio.protocol.HttpAsyncRequestExecutor.responseReceived(HttpAsyncRequestExecutor.java:309)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:255)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
> Nov 22 02:24:55 at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
> Nov 22 02:24:55 ... 1 more
> {noformat}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43369=logs=dbe51908-4958-5c8c-9557-e10952d4259d=55d11a16-067d-538d-76a3-4c096a3a8e24
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31445) Split resource allocate/release related logic from FineGrainedSlotManager to TaskManagerTracker
[ https://issues.apache.org/jira/browse/FLINK-31445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31445: --- 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. > Split resource allocate/release related logic from FineGrainedSlotManager to > TaskManagerTracker > --- > > Key: FLINK-31445 > URL: https://issues.apache.org/jira/browse/FLINK-31445 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Weihua Hu >Assignee: Weihua Hu >Priority: Major > Labels: pull-request-available, stale-assigned > > Currently the FineGrainedSlotManager is response to slots allocations and > resources request/release. This makes the logical of FineGrainedSlotManager > complicated, So we will move task manager related work from > FineGrainedSlotManager to TaskManagerTracker, which already tracks task > managers but not including request/release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-29545) kafka consuming stop when trigger first checkpoint
[ https://issues.apache.org/jira/browse/FLINK-29545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-29545: --- Labels: pull-request-available stale-critical (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 issues has been marked as Critical but is unassigned and neither itself nor its Sub-Tasks have been updated for 14 days. I have gone ahead and marked it "stale-critical". If this ticket is critical, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > kafka consuming stop when trigger first checkpoint > -- > > Key: FLINK-29545 > URL: https://issues.apache.org/jira/browse/FLINK-29545 > Project: Flink > Issue Type: Bug > Components: Runtime / Checkpointing, Runtime / Network >Affects Versions: 1.13.3 >Reporter: xiaogang zhou >Priority: Critical > Labels: pull-request-available, stale-critical > Attachments: backpressure 100 busy 0.png, task acknowledge na.png, > task dag.png > > > the task dag is like attached file. the task is started to consume from > earliest offset, it will stop when the first checkpoint triggers. > > is it normal?, for sink is busy 0 and the second operator has 100 backpressure > > and check the checkpoint summary, we can find some of the sub task is n/a. > I tried to debug this issue and found in the > triggerCheckpointAsync , the > triggerCheckpointAsyncInMailbox took a lot time to call > > > looks like this has something to do with > logCheckpointProcessingDelay, Has any fix on this issue? > > > can anybody help me on this issue? > > > > > thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-30203) BatchPandasConversionTests.test_empty_to_pandas failed
[
https://issues.apache.org/jira/browse/FLINK-30203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30203:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> BatchPandasConversionTests.test_empty_to_pandas failed
> --
>
> Key: FLINK-30203
> URL: https://issues.apache.org/jira/browse/FLINK-30203
> Project: Flink
> Issue Type: Bug
> Components: API / Python
>Affects Versions: 1.16.0, 1.15.3
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> [This
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43484=logs=3e4dd1a2-fe2f-5e5d-a581-48087e718d53=b4612f28-e3b5-5853-8a8b-610ae894217a=29175]
> failed (not exclusively) because of
> {{{}BatchPandasConversionTests.test_empty_to_pandas{}}}. Looks like it's
> caused by a {{{}NullPointerException{}}}:
> {code:java}
> Nov 25 02:08:35 E py4j.protocol.Py4JJavaError: An error
> occurred while calling
> z:org.apache.flink.table.runtime.arrow.ArrowUtils.collectAsPandasDataFrame.
> Nov 25 02:08:35 E : java.lang.NullPointerException
> Nov 25 02:08:35 E at
> java.util.Objects.requireNonNull(Objects.java:203)
> Nov 25 02:08:35 E at
> org.apache.calcite.rel.metadata.RelMetadataQuery.(RelMetadataQuery.java:144)
> Nov 25 02:08:35 E at
> org.apache.calcite.rel.metadata.RelMetadataQuery.(RelMetadataQuery.java:108)
> Nov 25 02:08:35 E at
> org.apache.flink.table.planner.plan.metadata.FlinkRelMetadataQuery.(FlinkRelMetadataQuery.java:78)
> Nov 25 02:08:35 E at
> org.apache.flink.table.planner.plan.metadata.FlinkRelMetadataQuery.instance(FlinkRelMetadataQuery.java:59)
> Nov 25 02:08:35 E at
> org.apache.flink.table.planner.calcite.FlinkRelOptClusterFactory$$anon$1.get(FlinkRelOptClusterFactory.scala:39)
> Nov 25 02:08:35 E at
> org.apache.flink.table.planner.calcite.FlinkRelOptClusterFactory$$anon$1.get(FlinkRelOptClusterFactory.scala:38)
> Nov 25 02:08:35 E at
> org.apache.calcite.plan.RelOptCluster.getMetadataQuery(RelOptCluster.java:178)
> Nov 25 02:08:35 E at
> org.apache.calcite.rel.logical.LogicalFilter.create(LogicalFilter.java:127)
> [...] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-29315) HDFSTest#testBlobServerRecovery fails on CI
[
https://issues.apache.org/jira/browse/FLINK-29315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29315:
---
Labels: pull-request-available stale-critical (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 issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> HDFSTest#testBlobServerRecovery fails on CI
> ---
>
> Key: FLINK-29315
> URL: https://issues.apache.org/jira/browse/FLINK-29315
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / FileSystem, Test Infrastructure, Tests
>Affects Versions: 1.16.0, 1.17.0, 1.15.3
>Reporter: Chesnay Schepler
>Priority: Critical
> Labels: pull-request-available, stale-critical
>
> The test started failing 2 days ago on different branches. I suspect
> something's wrong with the CI infrastructure.
> {code:java}
> Sep 15 09:11:22 [ERROR] Failures:
> Sep 15 09:11:22 [ERROR] HDFSTest.testBlobServerRecovery Multiple Failures
> (2 failures)
> Sep 15 09:11:22 java.lang.AssertionError: Test failed Error while
> running command to get file permissions : java.io.IOException: Cannot run
> program "ls": error=1, Operation not permitted
> Sep 15 09:11:22 at
> java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.Shell.runCommand(Shell.java:913)
> Sep 15 09:11:22 at org.apache.hadoop.util.Shell.run(Shell.java:869)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1170)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.Shell.execCommand(Shell.java:1264)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.Shell.execCommand(Shell.java:1246)
> Sep 15 09:11:22 at
> org.apache.hadoop.fs.FileUtil.execCommand(FileUtil.java:1089)
> Sep 15 09:11:22 at
> org.apache.hadoop.fs.RawLocalFileSystem$DeprecatedRawLocalFileStatus.loadPermissionInfo(RawLocalFileSystem.java:697)
> Sep 15 09:11:22 at
> org.apache.hadoop.fs.RawLocalFileSystem$DeprecatedRawLocalFileStatus.getPermission(RawLocalFileSystem.java:672)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.DiskChecker.mkdirsWithExistsAndPermissionCheck(DiskChecker.java:233)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.DiskChecker.checkDirInternal(DiskChecker.java:141)
> Sep 15 09:11:22 at
> org.apache.hadoop.util.DiskChecker.checkDir(DiskChecker.java:116)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.server.datanode.DataNode$DataNodeDiskChecker.checkDir(DataNode.java:2580)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.server.datanode.DataNode.checkStorageLocations(DataNode.java:2622)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2604)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2497)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.MiniDFSCluster.startDataNodes(MiniDFSCluster.java:1501)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:851)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:485)
> Sep 15 09:11:22 at
> org.apache.hadoop.hdfs.MiniDFSCluster$Builder.build(MiniDFSCluster.java:444)
> Sep 15 09:11:22 at
> org.apache.flink.hdfstests.HDFSTest.createHDFS(HDFSTest.java:93)
> Sep 15 09:11:22 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> Sep 15 09:11:22 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Sep 15 09:11:22 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Sep 15 09:11:22 at
> java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> Sep 15 09:11:22 ... 67 more
> Sep 15 09:11:22
> Sep 15 09:11:22 java.lang.NullPointerException:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26614) Upsert Kafka SQL Connector:Support startup mode of timestamp and specific offsets
[ https://issues.apache.org/jira/browse/FLINK-26614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26614: --- Labels: auto-deprioritized-major pull-request-available stale-minor (was: auto-deprioritized-major 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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Upsert Kafka SQL Connector:Support startup mode of timestamp and specific > offsets > - > > Key: FLINK-26614 > URL: https://issues.apache.org/jira/browse/FLINK-26614 > Project: Flink > Issue Type: New Feature > Components: Connectors / Kafka >Affects Versions: 1.14.4 >Reporter: Ning Ma >Priority: Minor > Labels: auto-deprioritized-major, pull-request-available, > stale-minor > > When we run Flink SQL using upsert-kafka connector, it cannot support startup > mode of timestamp or specific offsets. It is determined to read data from the > earliest. > I don't think it's reasonable. Because the data stored in Kafka is incomplete > that it only saves data for 7 days in most cases. So why don't we consume > data from the specified timestamp or offsets, and this can improve the > efficiency of reading data from Kafka. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26837) KafkaSinkE2ECase.testMetrics failed on azure
[
https://issues.apache.org/jira/browse/FLINK-26837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26837:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> KafkaSinkE2ECase.testMetrics failed on azure
>
>
> Key: FLINK-26837
> URL: https://issues.apache.org/jira/browse/FLINK-26837
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.15.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> 2022-03-23T11:31:24.8110184Z Mar 23 11:31:24 [INFO] Tests run: 1, Failures:
> 0, Errors: 0, Skipped: 0, Time elapsed: 41.644 s - in
> org.apache.flink.tests.util.kafka.SmokeKafkaITCase
> 2022-03-23T11:31:24.8211872Z Mar 23 11:31:24 [INFO] Running
> org.apache.flink.tests.util.kafka.KafkaSinkE2ECase
> 2022-03-23T11:34:19.9737001Z Mar 23 11:34:19 [ERROR] Tests run: 10, Failures:
> 0, Errors: 1, Skipped: 0, Time elapsed: 175.144 s <<< FAILURE! - in
> org.apache.flink.tests.util.kafka.KafkaSinkE2ECase
> 2022-03-23T11:34:19.9745550Z Mar 23 11:34:19 [ERROR]
> org.apache.flink.tests.util.kafka.KafkaSinkE2ECase.testMetrics(TestEnvironment,
> DataStreamSinkExternalContext, CheckpointingMode)[1] Time elapsed: 33.671 s
> <<< ERROR!
> 2022-03-23T11:34:19.9746518Z Mar 23 11:34:19
> java.util.concurrent.TimeoutException: Some tasks are not running until
> timeout
> 2022-03-23T11:34:19.9747987Z Mar 23 11:34:19 at
> org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:167)
> 2022-03-23T11:34:19.9748809Z Mar 23 11:34:19 at
> org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:152)
> 2022-03-23T11:34:19.9749807Z Mar 23 11:34:19 at
> org.apache.flink.runtime.testutils.CommonTestUtils.waitForAllTaskRunning(CommonTestUtils.java:235)
> 2022-03-23T11:34:19.9761004Z Mar 23 11:34:19 at
> org.apache.flink.connector.testframe.testsuites.SinkTestSuiteBase.testMetrics(SinkTestSuiteBase.java:390)
> 2022-03-23T11:34:19.9761886Z Mar 23 11:34:19 at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2022-03-23T11:34:19.9762592Z Mar 23 11:34:19 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 2022-03-23T11:34:19.9763357Z Mar 23 11:34:19 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 2022-03-23T11:34:19.9764073Z Mar 23 11:34:19 at
> java.lang.reflect.Method.invoke(Method.java:498)
> 2022-03-23T11:34:19.9764770Z Mar 23 11:34:19 at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
> 2022-03-23T11:34:19.9765525Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> 2022-03-23T11:34:19.9766388Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> 2022-03-23T11:34:19.9767243Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
> 2022-03-23T11:34:19.9768044Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
> 2022-03-23T11:34:19.9768879Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestTemplateMethod(TimeoutExtension.java:92)
> 2022-03-23T11:34:19.9769991Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
> 2022-03-23T11:34:19.9770865Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
> 2022-03-23T11:34:19.9771739Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> 2022-03-23T11:34:19.9772637Z Mar 23 11:34:19 at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> 2022-03-23T11:34:19.9822314Z Mar 23 11:34:19 at
>
[jira] [Updated] (FLINK-30327) Adding a values.schema.json to the Helm chart source to support schema validation on Helm chart configuration
[
https://issues.apache.org/jira/browse/FLINK-30327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30327:
---
Labels: stale-major starter (was: starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Adding a values.schema.json to the Helm chart source to support schema
> validation on Helm chart configuration
> -
>
> Key: FLINK-30327
> URL: https://issues.apache.org/jira/browse/FLINK-30327
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
>Affects Versions: kubernetes-operator-1.2.0
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, starter
>
> Helm charts support [configuration
> validation|https://helm.sh/docs/topics/charts/#schema-files] through
> {{{}values.schema.json{}}}. I'm wondering whether that's something worth
> adding.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26724) FlinkKafkaProducerMigrationOperatorTest.testRestoreProducer failed on azure due to Container startup failed
[
https://issues.apache.org/jira/browse/FLINK-26724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26724:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> FlinkKafkaProducerMigrationOperatorTest.testRestoreProducer failed on azure
> due to Container startup failed
> ---
>
> Key: FLINK-26724
> URL: https://issues.apache.org/jira/browse/FLINK-26724
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> 2022-03-17T10:27:56.1372771Z Mar 17 10:27:56
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed
> 2022-03-17T10:27:56.1373469Z Mar 17 10:27:56 at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:336)
> 2022-03-17T10:27:56.1376022Z Mar 17 10:27:56 at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
> 2022-03-17T10:27:56.1376901Z Mar 17 10:27:56 at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> 2022-03-17T10:27:56.1377769Z Mar 17 10:27:56 at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
> 2022-03-17T10:27:56.1378489Z Mar 17 10:27:56 at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> 2022-03-17T10:27:56.1379198Z Mar 17 10:27:56 at
> java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
> 2022-03-17T10:27:56.1379892Z Mar 17 10:27:56 at
> java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
> 2022-03-17T10:27:56.1380595Z Mar 17 10:27:56 at
> java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> 2022-03-17T10:27:56.1381267Z Mar 17 10:27:56 at
> java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:401)
> 2022-03-17T10:27:56.1381934Z Mar 17 10:27:56 at
> java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:734)
> 2022-03-17T10:27:56.1382658Z Mar 17 10:27:56 at
> java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
> 2022-03-17T10:27:56.1383409Z Mar 17 10:27:56 at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
> 2022-03-17T10:27:56.1384358Z Mar 17 10:27:56 at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
> 2022-03-17T10:27:56.1385680Z Mar 17 10:27:56 at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> 2022-03-17T10:27:56.1386625Z Mar 17 10:27:56 at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
> 2022-03-17T10:27:56.1387496Z Mar 17 10:27:56 at
> org.apache.flink.streaming.connectors.kafka.KafkaTestEnvironmentImpl.startKafkaContainerCluster(KafkaTestEnvironmentImpl.java:410)
> 2022-03-17T10:27:56.1388721Z Mar 17 10:27:56 at
> org.apache.flink.streaming.connectors.kafka.KafkaTestEnvironmentImpl.prepare(KafkaTestEnvironmentImpl.java:106)
> 2022-03-17T10:27:56.1389705Z Mar 17 10:27:56 at
> org.apache.flink.streaming.connectors.kafka.KafkaTestBase.startClusters(KafkaTestBase.java:159)
> 2022-03-17T10:27:56.1390910Z Mar 17 10:27:56 at
> org.apache.flink.streaming.connectors.kafka.KafkaTestBase.startClusters(KafkaTestBase.java:142)
> 2022-03-17T10:27:56.1392365Z Mar 17 10:27:56 at
> org.apache.flink.streaming.connectors.kafka.KafkaMigrationTestBase.testRestoreProducer(KafkaMigrationTestBase.java:134)
> 2022-03-17T10:27:56.1393179Z Mar 17 10:27:56 at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2022-03-17T10:27:56.1393963Z Mar 17 10:27:56 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 2022-03-17T10:27:56.1394714Z Mar 17 10:27:56 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 2022-03-17T10:27:56.1395908Z Mar 17 10:27:56 at
> java.lang.reflect.Method.invoke(Method.java:498)
> 2022-03-17T10:27:56.1397053Z Mar 17 10:27:56 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> 2022-03-17T10:27:56.1398364Z Mar 17 10:27:56 at
>
[jira] [Updated] (FLINK-26566) FlinkKafkaProducerITCase.testFailAndRecoverSameCheckpointTwice failed on azure
[
https://issues.apache.org/jira/browse/FLINK-26566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26566:
---
Labels: auto-deprioritized-major stale-minor test-stability (was:
auto-deprioritized-major test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> FlinkKafkaProducerITCase.testFailAndRecoverSameCheckpointTwice failed on azure
> --
>
> Key: FLINK-26566
> URL: https://issues.apache.org/jira/browse/FLINK-26566
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.14.3
>Reporter: Yun Gao
>Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, test-stability
>
> {code:java}
> Mar 09 20:11:28 [ERROR] Tests run: 15, Failures: 1, Errors: 0, Skipped: 0,
> Time elapsed: 274.396 s <<< FAILURE! - in
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducerITCase
> Mar 09 20:11:28 [ERROR] testFailAndRecoverSameCheckpointTwice Time elapsed:
> 74.511 s <<< FAILURE!
> Mar 09 20:11:28 java.lang.AssertionError: Expected elements: <[42, 43]>, but
> was: elements: <[42, 43, 42, 43, 42, 43, 42, 43]>
> Mar 09 20:11:28 at org.junit.Assert.fail(Assert.java:89)
> Mar 09 20:11:28 at
> org.apache.flink.streaming.connectors.kafka.KafkaTestBase.assertExactlyOnceForTopic(KafkaTestBase.java:331)
> Mar 09 20:11:28 at
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducerITCase.testFailAndRecoverSameCheckpointTwice(FlinkKafkaProducerITCase.java:316)
> Mar 09 20:11:28 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> Mar 09 20:11:28 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Mar 09 20:11:28 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Mar 09 20:11:28 at java.lang.reflect.Method.invoke(Method.java:498)
> Mar 09 20:11:28 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> Mar 09 20:11:28 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> Mar 09 20:11:28 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> Mar 09 20:11:28 at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> Mar 09 20:11:28 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> Mar 09 20:11:28 at
> org.apache.flink.testutils.junit.RetryRule$RetryOnFailureStatement.evaluate(RetryRule.java:135)
> Mar 09 20:11:28 at
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> Mar 09 20:11:28 at
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Mar 09 20:11:28 at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> Mar 09 20:11:28 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> Mar 09 20:11:28 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> Mar 09 20:11:28 at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> Mar 09 20:11:28 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> Mar 09 20:11:28 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=32778=logs=c5f0071e-1851-543e-9a45-9ac140befc32=15a22db7-8faa-5b34-3920-d33c9f0ca23c=7412
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30484) ZooKeeperLeaderElectionTest.testZooKeeperReelection timed out
[
https://issues.apache.org/jira/browse/FLINK-30484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30484:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> ZooKeeperLeaderElectionTest.testZooKeeperReelection timed out
> -
>
> Key: FLINK-30484
> URL: https://issues.apache.org/jira/browse/FLINK-30484
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
>Affects Versions: 1.15.3
>Reporter: Matthias Pohl
>Priority: Major
> Labels: stale-major, test-stability
>
> {{ZooKeeperLeaderElectionTest.testZooKeeperReelection}} timed out in
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44161=logs=4d4a0d10-fca2-5507-8eed-c07f0bdf4887=7b25afdf-cc6c-566f-5459-359dc2585798=15416
> {code}
> Dec 22 05:00:20 "main" #1 prio=5 os_prio=0 tid=0x7f1c7c00b800 nid=0x1ebdc
> waiting on condition [0x7f1c82b31000]
> Dec 22 05:00:20java.lang.Thread.State: WAITING (parking)
> Dec 22 05:00:20 at sun.misc.Unsafe.park(Native Method)
> Dec 22 05:00:20 - parking to wait for <0x8070b7c0> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> Dec 22 05:00:20 at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> Dec 22 05:00:20 at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> Dec 22 05:00:20 at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> Dec 22 05:00:20 at
> org.apache.flink.runtime.leaderelection.TestingRetrievalBase.lambda$waitForNewLeader$0(TestingRetrievalBase.java:50)
> Dec 22 05:00:20 at
> org.apache.flink.runtime.leaderelection.TestingRetrievalBase$$Lambda$310/1033917063.get(Unknown
> Source)
> Dec 22 05:00:20 at
> org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:144)
> Dec 22 05:00:20 at
> org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:138)
> Dec 22 05:00:20 at
> org.apache.flink.runtime.leaderelection.TestingRetrievalBase.waitForNewLeader(TestingRetrievalBase.java:48)
> Dec 22 05:00:20 at
> org.apache.flink.runtime.leaderelection.ZooKeeperLeaderElectionTest.testZooKeeperReelection(ZooKeeperLeaderElectionTest.java:238)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31427) Pulsar Catalog support with Schema translation
[ https://issues.apache.org/jira/browse/FLINK-31427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31427: --- 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. > Pulsar Catalog support with Schema translation > -- > > Key: FLINK-31427 > URL: https://issues.apache.org/jira/browse/FLINK-31427 > Project: Flink > Issue Type: Sub-task > Components: Connectors / Pulsar >Affects Versions: pulsar-4.0.0 >Reporter: Yufan Sheng >Assignee: Yufan Sheng >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: pulsar-4.0.1 > > > This task will make the Pulsar serve as the Flink catalog. It will expose the > Pulsar's namespace as the Flink's database, the topic as the Flink's table. > You can easily create a table and database on Pulsar. The table can be > consumed by other clients with a valid schema check. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31542) FatalExceptionClassifier#isFatal returns false if the exception is fatal
[
https://issues.apache.org/jira/browse/FLINK-31542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31542:
---
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.
> FatalExceptionClassifier#isFatal returns false if the exception is fatal
>
>
> Key: FLINK-31542
> URL: https://issues.apache.org/jira/browse/FLINK-31542
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Common
>Affects Versions: 1.16.0
>Reporter: Samuel Siebenmann
>Assignee: DavidLiu
>Priority: Minor
> Labels: pull-request-available, stale-assigned
>
> FatalExceptionClassifier#isFatal returns `false` if the passed throwable is
> fatal and `true` if it is not:
> {code:java}
> public boolean isFatal(Throwable err, Consumer throwableConsumer){
>
> if (validator.test(err)) {
> throwableConsumer.accept(throwableMapper.apply(err));
> return false;
> }
> if (chainedClassifier != null) {
> return chainedClassifier.isFatal(err, throwableConsumer);
> } else {
> return true;
> }
> }
> {code}
> ([github|https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-base/src/main/java/org/apache/flink/connector/base/sink/throwable/FatalExceptionClassifier.java#L44])
> However, the semantics of the method would indicate that it should return
> `true` if the passed throwable is fatal and `false` if it is not (i.e. the
> opposite of what is currently the case).
> Additionally, the method name doesn't clearly indicate its side effects.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26678) make flink-console.sh script clean
[
https://issues.apache.org/jira/browse/FLINK-26678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26678:
---
Labels: auto-deprioritized-major pull-request-available stale-minor (was:
auto-deprioritized-major 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 issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> make flink-console.sh script clean
> --
>
> Key: FLINK-26678
> URL: https://issues.apache.org/jira/browse/FLINK-26678
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Scripts
>Affects Versions: 1.16.0
>Reporter: Jacky Lau
>Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
>
> log_setting=("-Dlog.file=${log}"
> "-Dlog4j.configuration=file:${FLINK_CONF_DIR}/log4j-console.properties"
> "-Dlog4j.configurationFile=file:${FLINK_CONF_DIR}/log4j-console.properties"
> "-Dlogback.configurationFile=file:${FLINK_CONF_DIR}/logback-console.xml")
>
> we can use variable to replace log4j-console.properties
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31500) Move SqlAlterTableSchema conversion logic to AlterTableSchemaConverter
[
https://issues.apache.org/jira/browse/FLINK-31500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31500:
---
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.
> Move SqlAlterTableSchema conversion logic to AlterTableSchemaConverter
> --
>
> Key: FLINK-31500
> URL: https://issues.apache.org/jira/browse/FLINK-31500
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
>Reporter: Jark Wu
>Assignee: Ran Tao
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> Introduce {{AlterTableSchemaConverter}} and move the conversion logic of
> SqlAlterTableSchema -> AlterTableChangeOperation to it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31499) Move SqlCreateTable conversion logic to SqlCreateTableConverter
[
https://issues.apache.org/jira/browse/FLINK-31499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31499:
---
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.
> Move SqlCreateTable conversion logic to SqlCreateTableConverter
> ---
>
> Key: FLINK-31499
> URL: https://issues.apache.org/jira/browse/FLINK-31499
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
>Reporter: Jark Wu
>Assignee: xuzhiwen
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> Introduce {{SqlCreateTableConverter}} and move the conversion logic of
> SqlCreateTable -> CreateTableOperation to it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-26565) Use lateTrigger when the window maxtimestap of data is less than currentwatermark and it is not discarded because the allow latency parameter
[ https://issues.apache.org/jira/browse/FLINK-26565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26565: --- Labels: pull-request-available stale-minor (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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Use lateTrigger when the window maxtimestap of data is less than > currentwatermark and it is not discarded because the allow latency parameter > --- > > Key: FLINK-26565 > URL: https://issues.apache.org/jira/browse/FLINK-26565 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API, Table SQL / Planner, Table SQL / Runtime >Reporter: hehuiyuan >Priority: Minor > Labels: pull-request-available, stale-minor > Attachments: image-2022-03-10-11-27-52-891.png > > > Use lateTrigger when the window maxtimestap of data is less than > currentwatermark . > The data is not discarded because the allow latency parameter. > The lateTrigger is set and the window just appeared with this data. > !image-2022-03-10-11-27-52-891.png|width=543,height=318! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26601) Flink HBase HBaseRowDataAsyncLookupFunction threadPool not close cause container has so many 'hbase-async-lookup-worker' thread
[ https://issues.apache.org/jira/browse/FLINK-26601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26601: --- Labels: auto-deprioritized-major pull-request-available stale-minor (was: auto-deprioritized-major 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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Flink HBase HBaseRowDataAsyncLookupFunction threadPool not close cause > container has so many 'hbase-async-lookup-worker' thread > > > Key: FLINK-26601 > URL: https://issues.apache.org/jira/browse/FLINK-26601 > Project: Flink > Issue Type: Bug > Components: Connectors / HBase >Affects Versions: 1.13.0 >Reporter: zhisheng >Priority: Minor > Labels: auto-deprioritized-major, pull-request-available, > stale-minor > Attachments: image-2022-03-11-15-31-19-206.png, > image-2022-03-11-15-32-23-721.png, image-2022-03-11-15-32-46-701.png, > image-2022-03-11-15-32-58-084.png > > > [https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-hbase-2.2/src/main/java/org/apache/flink/connector/hbase2/source/HBaseRowDataAsyncLookupFunction.java#L111] > the thread pool create in the open function, but not gracefulShutdown in the > close function, when the job failover, it will renew the thread pool > !image-2022-03-11-15-32-58-084.png|width=516,height=288! > !image-2022-03-11-15-32-23-721.png|width=532,height=274! > !image-2022-03-11-15-31-19-206.png|width=555,height=369! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26581) Job supports the HADOOP_USER_NAME
[ https://issues.apache.org/jira/browse/FLINK-26581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26581: --- Labels: auto-deprioritized-major pull-request-available stale-minor (was: auto-deprioritized-major 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 issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Job supports the HADOOP_USER_NAME > -- > > Key: FLINK-26581 > URL: https://issues.apache.org/jira/browse/FLINK-26581 > Project: Flink > Issue Type: Improvement > Components: Deployment / YARN >Reporter: Bo Cui >Priority: Minor > Labels: auto-deprioritized-major, pull-request-available, > stale-minor > > in non-secure cluster，hadoop and yarn support HADOOP_USER_NAME, Flink can > also support it > [https://github.com/apache/flink/blob/4907f5fb7033b1f918c4e721a1ccf95878f980a2/flink-yarn/src/main/java/org/apache/flink/yarn/YarnClusterDescriptor.java#L1150] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31524) StreamDependencyTests.test_add_python_file failed
[
https://issues.apache.org/jira/browse/FLINK-31524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31524:
---
Labels: stale-assigned test-stability (was: test-stability)
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.
> StreamDependencyTests.test_add_python_file failed
> -
>
> Key: FLINK-31524
> URL: https://issues.apache.org/jira/browse/FLINK-31524
> Project: Flink
> Issue Type: Technical Debt
> Components: API / Python
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Assignee: Xingbo Huang
>Priority: Major
> Labels: stale-assigned, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=47318=logs=821b528f-1eed-5598-a3b4-7f748b13f261=6bb545dd-772d-5d8c-f258-f5085fba3295=24508
> Being caused by a "No module named 'test_dependency_manage_lib'" error:
> {code}
> [...]
> Mar 18 05:42:33 E Caused by:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException: Error
> received from SDK harness for instruction 1: Traceback (most recent call
> last):
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/.tox/py37-cython/lib/python3.7/site-packages/apache_beam/runners/worker/sdk_worker.py",
> line 287, in _execute
> Mar 18 05:42:33 E response = task()
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/.tox/py37-cython/lib/python3.7/site-packages/apache_beam/runners/worker/sdk_worker.py",
> line 360, in
> Mar 18 05:42:33 E lambda:
> self.create_worker().do_instruction(request), request)
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/.tox/py37-cython/lib/python3.7/site-packages/apache_beam/runners/worker/sdk_worker.py",
> line 597, in do_instruction
> Mar 18 05:42:33 E getattr(request, request_type),
> request.instruction_id)
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/.tox/py37-cython/lib/python3.7/site-packages/apache_beam/runners/worker/sdk_worker.py",
> line 634, in process_bundle
> Mar 18 05:42:33 E
> bundle_processor.process_bundle(instruction_id))
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/.tox/py37-cython/lib/python3.7/site-packages/apache_beam/runners/worker/bundle_processor.py",
> line 1004, in process_bundle
> Mar 18 05:42:33 E element.data)
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/.tox/py37-cython/lib/python3.7/site-packages/apache_beam/runners/worker/bundle_processor.py",
> line 227, in process_encoded
> Mar 18 05:42:33 E self.output(decoded_value)
> Mar 18 05:42:33 E File
> "apache_beam/runners/worker/operations.py", line 526, in
> apache_beam.runners.worker.operations.Operation.output
> Mar 18 05:42:33 E File
> "apache_beam/runners/worker/operations.py", line 528, in
> apache_beam.runners.worker.operations.Operation.output
> Mar 18 05:42:33 E File
> "apache_beam/runners/worker/operations.py", line 237, in
> apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
> Mar 18 05:42:33 E File
> "apache_beam/runners/worker/operations.py", line 240, in
> apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
> Mar 18 05:42:33 E File
> "pyflink/fn_execution/beam/beam_operations_fast.pyx", line 169, in
> pyflink.fn_execution.beam.beam_operations_fast.FunctionOperation.process
> Mar 18 05:42:33 E File
> "pyflink/fn_execution/beam/beam_operations_fast.pyx", line 196, in
> pyflink.fn_execution.beam.beam_operations_fast.FunctionOperation.process
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/pyflink/fn_execution/table/operations.py", line 110,
> in process_element
> Mar 18 05:42:33 E return self.func(value)
> Mar 18 05:42:33 E File "", line 1, in
> Mar 18 05:42:33 E File
> "/__w/1/s/flink-python/pyflink/table/tests/test_dependency.py", line 51, in
> plus_two
> Mar 18 05:42:33 E
[jira] [Updated] (FLINK-31520) Move SqlXXXModel conversion logic to SqlNodeConverter
[ https://issues.apache.org/jira/browse/FLINK-31520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31520: --- 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. > Move SqlXXXModel conversion logic to SqlNodeConverter > - > > Key: FLINK-31520 > URL: https://issues.apache.org/jira/browse/FLINK-31520 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / Planner >Reporter: xuzhiwen >Assignee: xuzhiwen >Priority: Major > Labels: pull-request-available, stale-assigned > > Introduce SqlNodeConverter for SqlModule-related conversion logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31528) Move SqlXXXCatalog conversion logic to SqlNodeConverter
[ https://issues.apache.org/jira/browse/FLINK-31528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-31528: --- 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. > Move SqlXXXCatalog conversion logic to SqlNodeConverter > --- > > Key: FLINK-31528 > URL: https://issues.apache.org/jira/browse/FLINK-31528 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / Planner >Reporter: xuzhiwen >Assignee: xuzhiwen >Priority: Major > Labels: pull-request-available, stale-assigned > > Introduce SqlNodeConverter for SqlCatalog-related conversion logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31518) HighAvailabilityServiceUtils resolves wrong webMonitorAddress in Standalone mode
[
https://issues.apache.org/jira/browse/FLINK-31518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31518:
---
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.
> HighAvailabilityServiceUtils resolves wrong webMonitorAddress in Standalone
> mode
>
>
> Key: FLINK-31518
> URL: https://issues.apache.org/jira/browse/FLINK-31518
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration, Runtime / REST
>Affects Versions: 1.16.0, 1.17.0, 1.16.1, 1.17.1
>Reporter: Vineeth Naroju
>Assignee: Samrat Deb
>Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.18.0
>
>
> {{HighAvailabilityServiceUtils#createHighAvailabilityServices()}} in
> {{HighAvailabilityMode.NONE}} mode uses
> {{HighAvailabilityServiceUtils#getWebMonitorAddress()}} to get web monitor
> address.
> {{HighAvailabilityServiceUtils#getWebMonitorAddress()}} reads only from
> {{rest.port}} in {{flink-conf.yaml}} . If {{rest.port}} is not enabled, then
> it returns {{0}} port number. It should dynamically fetch port number if
> {{rest.port}} is disabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-31501) Move SqlCreateView conversion logic to SqlCreateViewConverter
[
https://issues.apache.org/jira/browse/FLINK-31501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31501:
---
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.
> Move SqlCreateView conversion logic to SqlCreateViewConverter
> -
>
> Key: FLINK-31501
> URL: https://issues.apache.org/jira/browse/FLINK-31501
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
>Reporter: Jark Wu
>Assignee: Jark Wu
>Priority: Major
> Labels: pull-request-available, stale-assigned
>
> Introduce {{SqlCreateViewConverter}} and move the conversion logic of
> SqlCreateView -> CreateViewOperation to it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
