[jira] [Created] (FLINK-22816) Investigate feasibility of supporting multiple RM leader sessions within JM process
Xintong Song created FLINK-22816: Summary: Investigate feasibility of supporting multiple RM leader sessions within JM process Key: FLINK-22816 URL: https://issues.apache.org/jira/browse/FLINK-22816 Project: Flink Issue Type: Improvement Components: Runtime / Coordination Reporter: Xintong Song In FLINK-21667, we decoupled RM leadership and lifecycle managements. RM is not started after obtaining leadership, and stopped on losing leadership. Ideally, we may start and stop multiple RMs, as the process obtains and loses leadership. However, as discussed in the [PR|https://github.com/apache/flink/pull/15524#pullrequestreview-663987547], having a process to start multiple RMs may cause problems in some deployment modes. E.g., repeated AM registration is not allowed on Yarn. We need to investigate for all deployments that: - Whether having multiple leader sessions causes problems. - If it does, what can we do to solve the problem. For information, multi-leader-session support for RM has been implemented in FLINK-21667, but is disabled by default. To enable, add the system property "flink.tests.enable-rm-multi-leader-session". -- This message was sent by Atlassian Jira (v8.3.4#803005)
How to use or configure flink checkpointing with siddhi internal state
Hi , I was trying to do checkpointing while using siddhi as the CEP engine running on flink. While using siddhi windowing , it uses an internal state to aggregated or perform operation on a bucket of events pertaining to a specific time window. But what i am not sure is how can that state be mapped to Flinks internal state so that i can use flink checkpointing to safeguard the internal state of the siddhi operators in the face of failure. Any help or pointer for this will be of great help to me.Thanks in advance. Dipanjan -
[jira] [Created] (FLINK-22815) Disable unaligned checkpoints for broadcast partitioning
Dawid Wysakowicz created FLINK-22815: Summary: Disable unaligned checkpoints for broadcast partitioning Key: FLINK-22815 URL: https://issues.apache.org/jira/browse/FLINK-22815 Project: Flink Issue Type: Bug Components: Runtime / Checkpointing Affects Versions: 1.12.4, 1.13.1 Reporter: Dawid Wysakowicz Assignee: Dawid Wysakowicz Fix For: 1.14.0, 1.12.5, 1.13.2 Broadcast partitioning can not work with unaligned checkpointing. There are no guarantees that records are consumed at the same rate in all channels. This can result in some tasks applying state changes corresponding to a certain broadcasted event while others don't. In turn upon restore, it may lead to an inconsistent state. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLINK-22814) New sources are not defining/exposing checkpointStartDelayNanos metric
Piotr Nowojski created FLINK-22814: -- Summary: New sources are not defining/exposing checkpointStartDelayNanos metric Key: FLINK-22814 URL: https://issues.apache.org/jira/browse/FLINK-22814 Project: Flink Issue Type: Bug Components: API / DataStream, Runtime / Metrics Affects Versions: 1.12.4, 1.13.1 Reporter: Piotr Nowojski Assignee: Piotr Nowojski checkpointStartDelayNanos metric for new (FLIP-27) sources is always 0ms in the WebUI, regardless how long it took to finally start triggering the checkpoint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLINK-22813) Drop usages of legacy planner in Hive module
Timo Walther created FLINK-22813:
Summary: Drop usages of legacy planner in Hive module
Key: FLINK-22813
URL: https://issues.apache.org/jira/browse/FLINK-22813
Project: Flink
Issue Type: Sub-task
Components: Connectors / Hive, Table SQL / Ecosystem, Table SQL /
Legacy Planner
Reporter: Timo Walther
Assignee: Timo Walther
Remove references to {{flink-table-planner}} in the Hive module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[DISCUSS] Dashboard/HistoryServer authentication
Hi team, Firstly I would like to introduce Gabor or G [1] for short to the community, he is a Spark committer who has recently transitioned to the Flink Engineering team at Cloudera and is looking forward to contributing to Apache Flink. Previously G primarily focused on Spark Streaming and security. Based on requests from our customers G has implemented Kerberos and HTTP Basic Authentication for the Flink Dashboard and HistoryServer. Previously lacked an authentication story. We are looking to contribute this functionality back to the community, we believe that given Flink's maturity there should be a common code solution for this general pattern. We are looking forward to your feedback on G's design. [2] [1] http://gaborsomogyi.com/ [2] https://docs.google.com/document/d/1NMPeJ9H0G49TGy3AzTVVJVKmYC0okwOtqLTSPnGqzHw/edit
[jira] [Created] (FLINK-22812) Fix hive issues in sql-connector-hive jars
Rui Li created FLINK-22812: -- Summary: Fix hive issues in sql-connector-hive jars Key: FLINK-22812 URL: https://issues.apache.org/jira/browse/FLINK-22812 Project: Flink Issue Type: Improvement Components: Connectors / Hive Environment: Since we provide uber jars for hive connector, this gives us a chance to fix some hive issues on our side. Reporter: Rui Li Assignee: Rui Li -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [ANNOUNCE] Apache Flink 1.13.1 released
Thanks for the great work Dawid and to everyone who has contributed to this release. Cheers, Till On Mon, May 31, 2021 at 10:25 AM Yangze Guo wrote: > Thanks, Dawid for the great work, thanks to everyone involved. > > Best, > Yangze Guo > > On Mon, May 31, 2021 at 4:14 PM Youngwoo Kim (김영우) > wrote: > > > > Got it. > > Thanks Dawid for the clarification. > > > > - Youngwoo > > > > On Mon, May 31, 2021 at 4:50 PM Dawid Wysakowicz > wrote: > >> > >> Hi Youngwoo, > >> > >> Usually we publish the docker images a day after the general release, so > >> that the artifacts are properly distributed across Apache mirrors. You > >> should be able to download the docker images from apache/flink now. It > >> may take a few extra days to have the images published as the official > >> image, as it depends on the maintainers of docker hub. > >> > >> Best, > >> > >> Dawid > >> > >> On 31/05/2021 08:01, Youngwoo Kim (김영우) wrote: > >> > Great work! Thank you Dawid and all of the contributors. > >> > I'm eager to adopt the new release, however can't find docker images > for > >> > that from https://hub.docker.com/_/flink > >> > > >> > Hope it'll be available soon. > >> > > >> > Thanks, > >> > Youngwoo > >> > > >> > > >> > On Sat, May 29, 2021 at 1:49 AM Dawid Wysakowicz < > dwysakow...@apache.org> > >> > wrote: > >> > > >> >> The Apache Flink community is very happy to announce the release of > Apache > >> >> Flink 1.13.1, which is the first bugfix release for the Apache Flink > 1.13 > >> >> series. > >> >> > >> >> Apache Flink® is an open-source stream processing framework for > >> >> distributed, high-performing, always-available, and accurate data > streaming > >> >> applications. > >> >> > >> >> The release is available for download at: > >> >> https://flink.apache.org/downloads.html > >> >> > >> >> Please check out the release blog post for an overview of the > improvements > >> >> for this bugfix release: > >> >> https://flink.apache.org/news/2021/05/28/release-1.13.1.html > >> >> > >> >> The full release notes are available in Jira: > >> >> > >> >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350058 > >> >> > >> >> We would like to thank all contributors of the Apache Flink > community who > >> >> made this release possible! > >> >> > >> >> Regards, > >> >> Dawid Wysakowicz > >> >> > >> >
[jira] [Created] (FLINK-22811) Drop usages of legacy planner in Avro module
Timo Walther created FLINK-22811:
Summary: Drop usages of legacy planner in Avro module
Key: FLINK-22811
URL: https://issues.apache.org/jira/browse/FLINK-22811
Project: Flink
Issue Type: Sub-task
Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile), Table
SQL / Legacy Planner
Reporter: Timo Walther
Assignee: Timo Walther
Remove references to {{flink-table-planner}} in the Avro module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FLINK-22810) Drop usages of flink-table-planner in Elasticsearch modules
Timo Walther created FLINK-22810:
Summary: Drop usages of flink-table-planner in Elasticsearch
modules
Key: FLINK-22810
URL: https://issues.apache.org/jira/browse/FLINK-22810
Project: Flink
Issue Type: Sub-task
Components: Connectors / ElasticSearch, Table SQL / Legacy Planner
Reporter: Timo Walther
Assignee: Timo Walther
Remove references to {{flink-table-planner}} in al Elasticsearch modules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FLINK-22809) Improve the exception message when a KafkaIngress receives a NULL key.
Igal Shilman created FLINK-22809: Summary: Improve the exception message when a KafkaIngress receives a NULL key. Key: FLINK-22809 URL: https://issues.apache.org/jira/browse/FLINK-22809 Project: Flink Issue Type: Improvement Components: Stateful Functions Reporter: Igal Shilman Fix For: statefun-3.1.0 Mailing list discussion: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Statefun-2-2-2-Checkpoint-restore-NPE-td44022.html The following line throws a generic NPE, instead it should a bit more descriptive. https://github.com/apache/flink-statefun/blob/release-2.2/statefun-flink/statefun-flink-io-bundle/src/main/java/org/apache/flink/statefun/flink/io/kafka/RoutableProtobufKafkaIngressDeserializer.java#L48 -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS][Statebackend][Runtime] Changelog Statebackend Configuration Proposal
Hey Yuan, thanks for the proposal I think Option 3 is the simplest to use and exposes less details than any other. It's also consistent with the current way of configuring state backends, as long as we treat change logging as a common feature applicable to any state backend, like e.g. state.backend.local-recovery. Option 6 seems slightly less preferable as it exposes more details but I think is the most viable alternative. Regards, Roman On Mon, May 31, 2021 at 8:39 AM Yuan Mei wrote: > > Hey all, > > We would like to start a discussion on how to enable/config Changelog > Statebakcend. > > As part of FLIP-158[1], Changelog state backend wraps on top of existing > state backend (HashMapStateBackend, EmbeddedRocksDBStateBackend and may > expect more) and delegates state changes to the underlying state backends. > This thread is to discuss the problem of how Changelog StateBackend should > be enabled and configured. > > Proposed options to enable/config state changelog is listed below: > > Option 1: Enable Changelog Statebackend through a Boolean Flag > > Option 2: Enable Changelog Statebackend through a Boolean Flag + a Special > Case > > Option 3: Enable Changelog Statebackend through a Boolean Flag + W/O > ChangelogStateBackend Exposed > > Option 4: Explicit Nested Configuration + “changelog.inner” prefix for > inner backend > > Option 5: Explicit Nested Configuration + inner state backend configuration > unchanged > > Option 6: Config Changelog and Inner Statebackend All-Together > > Details of each option can be found here: > https://docs.google.com/document/d/13AaCf5fczYTDHZ4G1mgYL685FqbnoEhgo0cdwuJlZmw/edit?usp=sharing > > When considering these options, please consider these four dimensions: > 1 Consistency > API/config should follow a consistent model and should not have > contradicted logic beneath > 2 Simplicity > API should be easy to use and not introduce too much burden on users > 3. Explicity > API/config should not contain implicit assumptions and should be intuitive > to users > 4. Extensibility > With foreseen future, whether the current setting can be easily extended > > Please let us know what do you think and please keep the discussion in this > mailing thread. > > [1] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-158%3A+Generalized+incremental+checkpoints > > Best > Yuan
Re: [ANNOUNCE] Apache Flink 1.13.1 released
Thanks, Dawid for the great work, thanks to everyone involved. Best, Yangze Guo On Mon, May 31, 2021 at 4:14 PM Youngwoo Kim (김영우) wrote: > > Got it. > Thanks Dawid for the clarification. > > - Youngwoo > > On Mon, May 31, 2021 at 4:50 PM Dawid Wysakowicz > wrote: >> >> Hi Youngwoo, >> >> Usually we publish the docker images a day after the general release, so >> that the artifacts are properly distributed across Apache mirrors. You >> should be able to download the docker images from apache/flink now. It >> may take a few extra days to have the images published as the official >> image, as it depends on the maintainers of docker hub. >> >> Best, >> >> Dawid >> >> On 31/05/2021 08:01, Youngwoo Kim (김영우) wrote: >> > Great work! Thank you Dawid and all of the contributors. >> > I'm eager to adopt the new release, however can't find docker images for >> > that from https://hub.docker.com/_/flink >> > >> > Hope it'll be available soon. >> > >> > Thanks, >> > Youngwoo >> > >> > >> > On Sat, May 29, 2021 at 1:49 AM Dawid Wysakowicz >> > wrote: >> > >> >> The Apache Flink community is very happy to announce the release of Apache >> >> Flink 1.13.1, which is the first bugfix release for the Apache Flink 1.13 >> >> series. >> >> >> >> Apache Flink® is an open-source stream processing framework for >> >> distributed, high-performing, always-available, and accurate data >> >> streaming >> >> applications. >> >> >> >> The release is available for download at: >> >> https://flink.apache.org/downloads.html >> >> >> >> Please check out the release blog post for an overview of the improvements >> >> for this bugfix release: >> >> https://flink.apache.org/news/2021/05/28/release-1.13.1.html >> >> >> >> The full release notes are available in Jira: >> >> >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350058 >> >> >> >> We would like to thank all contributors of the Apache Flink community who >> >> made this release possible! >> >> >> >> Regards, >> >> Dawid Wysakowicz >> >> >>
Re: [ANNOUNCE] Apache Flink 1.13.1 released
Got it. Thanks Dawid for the clarification. - Youngwoo On Mon, May 31, 2021 at 4:50 PM Dawid Wysakowicz wrote: > Hi Youngwoo, > > Usually we publish the docker images a day after the general release, so > that the artifacts are properly distributed across Apache mirrors. You > should be able to download the docker images from apache/flink now. It > may take a few extra days to have the images published as the official > image, as it depends on the maintainers of docker hub. > > Best, > > Dawid > > On 31/05/2021 08:01, Youngwoo Kim (김영우) wrote: > > Great work! Thank you Dawid and all of the contributors. > > I'm eager to adopt the new release, however can't find docker images for > > that from https://hub.docker.com/_/flink > > > > Hope it'll be available soon. > > > > Thanks, > > Youngwoo > > > > > > On Sat, May 29, 2021 at 1:49 AM Dawid Wysakowicz > > > wrote: > > > >> The Apache Flink community is very happy to announce the release of > Apache > >> Flink 1.13.1, which is the first bugfix release for the Apache Flink > 1.13 > >> series. > >> > >> Apache Flink® is an open-source stream processing framework for > >> distributed, high-performing, always-available, and accurate data > streaming > >> applications. > >> > >> The release is available for download at: > >> https://flink.apache.org/downloads.html > >> > >> Please check out the release blog post for an overview of the > improvements > >> for this bugfix release: > >> https://flink.apache.org/news/2021/05/28/release-1.13.1.html > >> > >> The full release notes are available in Jira: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350058 > >> > >> We would like to thank all contributors of the Apache Flink community > who > >> made this release possible! > >> > >> Regards, > >> Dawid Wysakowicz > >> > >
Re: [ANNOUNCE] Apache Flink 1.13.1 released
Hi Youngwoo, Usually we publish the docker images a day after the general release, so that the artifacts are properly distributed across Apache mirrors. You should be able to download the docker images from apache/flink now. It may take a few extra days to have the images published as the official image, as it depends on the maintainers of docker hub. Best, Dawid On 31/05/2021 08:01, Youngwoo Kim (김영우) wrote: > Great work! Thank you Dawid and all of the contributors. > I'm eager to adopt the new release, however can't find docker images for > that from https://hub.docker.com/_/flink > > Hope it'll be available soon. > > Thanks, > Youngwoo > > > On Sat, May 29, 2021 at 1:49 AM Dawid Wysakowicz > wrote: > >> The Apache Flink community is very happy to announce the release of Apache >> Flink 1.13.1, which is the first bugfix release for the Apache Flink 1.13 >> series. >> >> Apache Flink® is an open-source stream processing framework for >> distributed, high-performing, always-available, and accurate data streaming >> applications. >> >> The release is available for download at: >> https://flink.apache.org/downloads.html >> >> Please check out the release blog post for an overview of the improvements >> for this bugfix release: >> https://flink.apache.org/news/2021/05/28/release-1.13.1.html >> >> The full release notes are available in Jira: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350058 >> >> We would like to thank all contributors of the Apache Flink community who >> made this release possible! >> >> Regards, >> Dawid Wysakowicz >> OpenPGP_signature Description: OpenPGP digital signature
[jira] [Created] (FLINK-22808) Log metadata
Roman Khachatryan created FLINK-22808: - Summary: Log metadata Key: FLINK-22808 URL: https://issues.apache.org/jira/browse/FLINK-22808 Project: Flink Issue Type: Sub-task Components: Runtime / State Backends Reporter: Roman Khachatryan Assignee: Roman Khachatryan Fix For: 1.14.0 In FLINK-21355, logging state changes was added. This ticket is about storing metadata in log so that changes can be applied on recovery (spun off from FLINK-21355 to ease review). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLINK-22807) AttributeError: 'Builder' object has no attribute 'is_streaming_mode'
Yao Li created FLINK-22807: -- Summary: AttributeError: 'Builder' object has no attribute 'is_streaming_mode' Key: FLINK-22807 URL: https://issues.apache.org/jira/browse/FLINK-22807 Project: Flink Issue Type: Bug Affects Versions: 1.13.0 Reporter: Yao Li Attachments: 5df1e86bb905e743a020d7d3b2589f7e.png 安装的v1.13版本pyflink模块, 创建环境对象时报错如下: >>> from pyflink.table import TableEnvironment,EnvironmentSettings >>> env_settings = >>> EnvironmentSettings.new_instance().use_blink_planner().is_streaming_mode().build() Traceback (most recent call last): File "", line 1, in AttributeError: 'Builder' object has no attribute 'is_streaming_mode' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSS][Statebackend][Runtime] Changelog Statebackend Configuration Proposal
Hey all, We would like to start a discussion on how to enable/config Changelog Statebakcend. As part of FLIP-158[1], Changelog state backend wraps on top of existing state backend (HashMapStateBackend, EmbeddedRocksDBStateBackend and may expect more) and delegates state changes to the underlying state backends. This thread is to discuss the problem of how Changelog StateBackend should be enabled and configured. Proposed options to enable/config state changelog is listed below: Option 1: Enable Changelog Statebackend through a Boolean Flag Option 2: Enable Changelog Statebackend through a Boolean Flag + a Special Case Option 3: Enable Changelog Statebackend through a Boolean Flag + W/O ChangelogStateBackend Exposed Option 4: Explicit Nested Configuration + “changelog.inner” prefix for inner backend Option 5: Explicit Nested Configuration + inner state backend configuration unchanged Option 6: Config Changelog and Inner Statebackend All-Together Details of each option can be found here: https://docs.google.com/document/d/13AaCf5fczYTDHZ4G1mgYL685FqbnoEhgo0cdwuJlZmw/edit?usp=sharing When considering these options, please consider these four dimensions: 1 Consistency API/config should follow a consistent model and should not have contradicted logic beneath 2 Simplicity API should be easy to use and not introduce too much burden on users 3. Explicity API/config should not contain implicit assumptions and should be intuitive to users 4. Extensibility With foreseen future, whether the current setting can be easily extended Please let us know what do you think and please keep the discussion in this mailing thread. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-158%3A+Generalized+incremental+checkpoints Best Yuan
Re: [DISCUSS] Watermark propagation with Sink API
Afaik everyone can start a [VOTE] thread [1]. For example, here a non-committer started a successful thread [2]. If you start it, I can already cast a binding vote and we just need 2 more for the FLIP to be accepted. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026#FlinkBylaws-Voting [2] http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Deprecating-Mesos-support-td50142.html On Fri, May 28, 2021 at 8:17 PM Eron Wright wrote: > Arvid, > Thanks for the feedback. I investigated the japicmp configuration, and I > see that SinkWriter is marked Experimental (not Public or PublicEvolving). > I think this means that SinkWriter need not be excluded. As you mentioned, > SinkFunction is already excluded. I've updated the FLIP with an > explanation. > > I believe all issues are resolved. May we proceed to a vote now? And are > you able to drive the vote process? > > Thanks, > Eron > > > On Fri, May 28, 2021 at 4:40 AM Arvid Heise wrote: > > > Hi Eron, > > > > 1. fair point. It still feels odd to have writeWatermark in the > > SinkFunction (it's supposed to be functional as you mentioned), but I > agree > > that invokeWatermark is not better. So unless someone has a better idea, > > I'm fine with it. > > 2.+3. I tried to come up with scenarios for a longer time. In general, it > > seems as if the new SinkWriter interface encourages more injection (see > > processing time service in InitContext), such that the need for the > context > > is really just context information of that particular record and I don't > > see any use beyond timestamp and watermark. For SinkFunction, I'd not > > over-engineer as it's going to be deprecated soonish. So +1 to leave it > > out. > > 4. Okay so I double-checked: from an execution perspective, it works. > > However, japicmp would definitely complain. I propose to add it to the > > compatibility section like this. We need to add an exception to > SinkWriter > > then. (SinkFunction is already on the exception list) > > 5.+6. Awesome, I was also sure but wanted to double check. > > > > Best, > > > > Arvid > > > > > > On Wed, May 26, 2021 at 7:29 PM Eron Wright > .invalid> > > wrote: > > > > > Arvid, > > > > > > 1. I assume that the method name `invoke` stems from considering the > > > SinkFunction to be a functional interface, but is otherwise > meaningless. > > > Keeping it as `writeWatermark` does keep it symmetric with SinkWriter. > > My > > > vote is to leave it. You decide. > > > > > > 2+3. I too considered adding a `WatermarkContext`, but it would merely > > be a > > > placeholder. I don't anticipate any context info in future. As we see > > > with invoke, it is possible to add a context later in a > > > backwards-compatible way. My vote is to not introduce a context. You > > > decide. > > > > > > 4. No anticipated compatibility issues. > > > > > > 5. Short answer, it works as expected. The new methods are invoked > > > whenever the underlying operator receives a watermark. I do believe > that > > > batch and ingestion time applications receive watermarks. Seems the > > > programming model is more unified in that respect since 1.12 > (FLIP-134). > > > > > > 6. The failure behavior is the same as for elements. > > > > > > Thanks, > > > Eron > > > > > > On Tue, May 25, 2021 at 12:42 PM Arvid Heise wrote: > > > > > > > Hi Eron, > > > > > > > > I think the FLIP is crisp and mostly good to go. Some smaller > > > > things/questions: > > > > > > > >1. SinkFunction#writeWatermark could be named > > > >SinkFunction#invokeWatermark or invokeOnWatermark to keep it > > > symmetric. > > > >2. We could add the context parameter to both. For > > SinkWriter#Context, > > > >we currently do not gain much. SinkFunction#Context also exposes > > > > processing > > > >time, which may or may not be handy and is currently mostly used > for > > > >StreamingFileSink bucket policies. We may add that processing time > > > flag > > > >also to SinkWriter#Context in the future. > > > >3. Alternatively, we could also add a different context parameter > > just > > > >to keep the API stable while allowing additional information to be > > > > passed > > > >in the future. > > > >4. Would we run into any compatibility issue if we use Flink 1.13 > > > source > > > >in Flink 1.14 (with this FLIP) or vice versa? > > > >5. What happens with sinks that use the new methods in > applications > > > that > > > >do not have watermarks (batch mode, processing time)? Does this > also > > > > work > > > >with ingestion time sufficiently? > > > >6. How do exactly once sinks deal with written watermarks in case > of > > > >failure? I guess it's the same as normal records. (Either rollback > > of > > > >transaction or deduplication on resumption) > > > > > > > > Best, > > > > > > > > Arvid > > > > > > > > On Tue, May 25, 2021 at 6:44 PM Eron Wright > > > .invalid> > > > > wrote: > > > > > > > > >
Re: [ANNOUNCE] Apache Flink 1.13.1 released
Great work! Thank you Dawid and all of the contributors. I'm eager to adopt the new release, however can't find docker images for that from https://hub.docker.com/_/flink Hope it'll be available soon. Thanks, Youngwoo On Sat, May 29, 2021 at 1:49 AM Dawid Wysakowicz wrote: > The Apache Flink community is very happy to announce the release of Apache > Flink 1.13.1, which is the first bugfix release for the Apache Flink 1.13 > series. > > Apache Flink® is an open-source stream processing framework for > distributed, high-performing, always-available, and accurate data streaming > applications. > > The release is available for download at: > https://flink.apache.org/downloads.html > > Please check out the release blog post for an overview of the improvements > for this bugfix release: > https://flink.apache.org/news/2021/05/28/release-1.13.1.html > > The full release notes are available in Jira: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350058 > > We would like to thank all contributors of the Apache Flink community who > made this release possible! > > Regards, > Dawid Wysakowicz >
