You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Hequn Cheng <ch...@gmail.com> on 2019/12/22 15:34:23 UTC

[ANNOUNCE] Weekly Community Update 2019/51

Dear community,

Happy to share this week's brief community digest with updates on Flink
1.10 and Flink 1.9.2, a proposal to integrate Flink Docker image
publication into Flink release process, a discussion on new features of
PyFlink and a couple of blog posts. Enjoy.

Flink Development
==============

* [releases] Kostas Kloudas suggests to focus a little bit on documenting
the new features that the community added to release-1.10 during the
feature-freeze phrase. He has created an umbrella issue(FLINK-15273) to
monitor the pending documentation tasks.[1]

* [releases] Hequn has started a conversation about the release of Flink
1.9.2. One blocker has been addressed this week but a new one is reported.
Considering the ongoing release-1.10 and the limited resources of the
community, the process of 1.9.2 is planned to slow down. [2]

* [releases] Patrick proposes to integrate Flink Docker image publication
into the Flink release process. There are some discussions on whether to
have a dedicated git repo for the Dockerfiles. [3]

* [sq] The discussion on supporting JSON functions in Flink SQL seems to
have reached an agreement. Jark Wu suggested Forward Xu to start a vote. [4]

* [runtime] Stephan raised a discussion and gives some feedback after
trying out the new FLIP-49 memory configurations. He gives some
alternatives on config key names and descriptions. The feedback received
many +1 from other ones. [5]

* [connectors] Some new updates for the discussion on Flip-27, the new
source interface. This has been a log ongoing topic. This week the
discussions are focused on the concept of BOUNDED AND UNBOUNDED for the
source.  [6]

* [pyflink] Jincheng has started a discussion on what parts of the Python
API should we focus on next. A default feature list is given but looking
forward to hearing more feedback from the community. [7]

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Documentation-tasks-for-release-1-10-td36031.html
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Releasing-Flink-1-9-2-td36087.html
[3]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Integrate-Flink-Docker-image-publication-into-Flink-release-process-td36139.html
[4]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Support-JSON-functions-in-Flink-SQL-td32674.html
[5]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Some-feedback-after-trying-out-the-new-FLIP-49-memory-configurations-td36129.html
[6]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-27-Refactor-Source-Interface-td24952.html
[7]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-What-parts-of-the-Python-API-should-we-focus-on-next-td36119.html

Notable Bugs
==========

[FLINK-15262] [1.10.0] kafka connector doesn't read from beginning
immediately when 'connector.startup-mode' = 'earliest-offset'. [8]
[FLINK-15300] [1.10.0] Shuffle memory fraction sanity check does not
account for its min/max limit. [9]
[FLINK-15304] [1.11.0] Remove unexpected Hadoop dependency from Flink's
Mesos integration. [10]
[FLINK-15313] [1.10.0] Can not insert decimal with precision into sink
using TypeInformation. [11]
[FLINK-15320] [1.10.0] JobManager crashes in the standalone model when
cancelling job which subtask' status is scheduled. [12]

[8] https://issues.apache.org/jira/browse/FLINK-15262
[9] https://issues.apache.org/jira/browse/FLINK-15300
[10] https://issues.apache.org/jira/browse/FLINK-15304
[11] https://issues.apache.org/jira/browse/FLINK-15313
[12] https://issues.apache.org/jira/browse/FLINK-15320

Events, Blog Posts, Misc
===================

* Philip Wilcox has published a blog about how they use Flink to detect
offline scooters in Bird. The blog mainly shares some experience of how to
solve a set of tricky problems involving Kafka, event time, watermarks, and
ordering. [13]

* In this blog post, Preetdeep Kumar introduces use-cases and best
practices for utilizing Apache Flink for processing streaming data. [14].

[13]
https://www.ververica.com/blog/replayable-process-functions-time-ordering-and-timers
[14] https://dzone.com/articles/streaming-etl-with-apache-flink

Cheers,
Hequn