Timo, thanks for the response. I have a few more questions.
as mentioned in "Scoping and Simplifications" a PTF will not support
> late events. It will filter them out. We have to solve the late events
> topic at an earlier stage in the SQL pipeline. This is a different FLIP
> discussion. Not ever
Jerome Gagnon created FLINK-36650:
-
Summary: ConfluentRegistryAvroSerializationSchema always tries to
register the schema on serialize even if it already exists
Key: FLINK-36650
URL: https://issues.apache.org/jira
Hi David,
as mentioned in "Scoping and Simplifications" a PTF will not support
late events. It will filter them out. We have to solve the late events
topic at an earlier stage in the SQL pipeline. This is a different FLIP
discussion. Not every SQL operators should deal with late events in a
d
Di Wu created FLINK-36649:
-
Summary: Oracle When reading via OracleIncrementalSource, the
connection is occasionally closed
Key: FLINK-36649
URL: https://issues.apache.org/jira/browse/FLINK-36649
Project: Fli
Hi Xuyang,
thanks for the good questions.
1. What happens if the TTLs for these different StateHints are not the same?
The eval() fully determines available state and their TTL. Helper
methods such as onTimer() and finish() can references a subset of
declared state. It is not necessary that t
> 3. Change of interfaces for multiple output tables
> Currently, I think using a STATEMENT SET should be enough for side
> output semantics. I have added an example in section 5.2.3.2 for that.
I question whether this really works. Is there a guarantee that
watermarking will be applied upstream o
