[jira] [Created] (FLINK-29052) Support TO_TIMESTAMP built-in function in Table API
hehuiyuan created FLINK-29052: - Summary: Support TO_TIMESTAMP built-in function in Table API Key: FLINK-29052 URL: https://issues.apache.org/jira/browse/FLINK-29052 Project: Flink Issue Type: Improvement Components: Table SQL / API Reporter: hehuiyuan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29051) Put dependency-reduced pom for quickstart in target folder
Sergey Nuyanzin created FLINK-29051: --- Summary: Put dependency-reduced pom for quickstart in target folder Key: FLINK-29051 URL: https://issues.apache.org/jira/browse/FLINK-29051 Project: Flink Issue Type: Improvement Components: Quickstarts Affects Versions: 1.15.1 Reporter: Sergey Nuyanzin now maven-shade-plugin puts it in project folder and version control detects as a change. The proposal is to put it to target folder as it's done for table-planner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29050) [JUnit5 Migration] Module: flink-hadoop-compatibility
RocMarshal created FLINK-29050: -- Summary: [JUnit5 Migration] Module: flink-hadoop-compatibility Key: FLINK-29050 URL: https://issues.apache.org/jira/browse/FLINK-29050 Project: Flink Issue Type: Sub-task Components: Connectors / Hadoop Compatibility, Tests Reporter: RocMarshal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29049) Remove the deprecated classes in the flink-java module.
RocMarshal created FLINK-29049: -- Summary: Remove the deprecated classes in the flink-java module. Key: FLINK-29049 URL: https://issues.apache.org/jira/browse/FLINK-29049 Project: Flink Issue Type: Technical Debt Reporter: RocMarshal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29048) WatermarksWithIdleness does not work with FLIP-27 sources
Lee Y S created FLINK-29048:
---
Summary: WatermarksWithIdleness does not work with FLIP-27 sources
Key: FLINK-29048
URL: https://issues.apache.org/jira/browse/FLINK-29048
Project: Flink
Issue Type: Bug
Components: API / DataStream
Affects Versions: 1.15.1
Reporter: Lee Y S
In org.apache.flink.streaming.api.operators.SourceOperator, there are separate
instances of WatermarksWithIdleness created for each split output and the main
output. There is multiplexing of watermarks between split outputs but no
multiplexing between split output and main output in
org.apache.flink.streaming.api.operators.source.ProgressiveTimestampsAndWatermarks.
For a source such as org.apache.flink.connector.kafka.source.KafkaSource,
{color:#353833}there is only output from splits and no output from main. Hence
the main output will (after an initial timeout) be marked as idle.{color}
{color:#353833} {color}
{color:#353833}The implementation of {color}WatermarksWithIdleness is such that
once an output is idle, it will periodically re-mark the output as idle. Since
there is no multiplexing between split outputs and main output, the idle marks
coming from main output will repeatedly set the output to idle even though
there are events from the splits. Result is that the entire source is
repeatedly marked as idle.
One solution i can think of is to multiplex split and main output in
org.apache.flink.streaming.api.operators.source.ProgressiveTimestampsAndWatermarks
but I am not sure if there are other considerations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
