[jira] [Created] (FLINK-21720) Rework Documentation Style Guide for the new build system

[Marta Paes Moreira (Jira)]

Marta Paes Moreira created FLINK-21720:
--

 Summary: Rework Documentation Style Guide for the new build system
 Key: FLINK-21720
 URL: https://issues.apache.org/jira/browse/FLINK-21720
 Project: Flink
  Issue Type: Task
  Components: Project Website
Reporter: Marta Paes Moreira
Assignee: Marta Paes Moreira


Since the docs build changed from Jekyll to Hugo 
([FLIP-157|https://cwiki.apache.org/confluence/display/FLINK/FLIP-157+Migrate+Flink+Documentation+from+Jekyll+to+Hugo]),
 the [style guide|https://flink.apache.org/contributing/docs-style.html] needs 
to be adapted accordingly. The changes should also cover the [chinese 
translation 
specification|https://flink.apache.org/contributing/docs-style.html].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Make SQL docs Blink only

[Marta Paes Moreira]

+1, this is confusing (esp. for new users) and also creates more and more
"annotation clutter" as new features are added.

On Tue, Dec 8, 2020 at 5:30 PM Aljoscha Krettek  wrote:

> +1
>
> Yes, please!
>
> On 08.12.20 16:52, David Anderson wrote:
> > I agree -- I think separating out the legacy planner info should make
> > things clearer for everyone, and then some day we can simply drop it.
> Plus,
> > doing it now will make it easier to make improvements to the docs going
> > forward.
> >
> > David
> >
> > On Tue, Dec 8, 2020 at 4:38 PM Timo Walther  wrote:
> >
> >> Hi Seth,
> >>
> >> this is a very good idea. We might not be able to remove the legacy
> >> planner immediately but at least we can make the docs easier for current
> >> and future users of the Blink planner.
> >>
> >> Making the SQL docs Blink-only with a dedicated legacy planner page
> >> sounds good to me.
> >>
> >> Regards,
> >> Timo
> >> On 08.12.20 16:36, Seth Wiesman wrote:
> >>> Hi Everyone,
> >>>
> >>> I've been spending a lot of time recently working on the SQL
> >> documentation
> >>> and I'm finding it very difficult to explain semantics as the two table
> >>> planners continue to diverge. As Blink has been the default planner for
> >>> some time, and 1.12 now offers bounded data stream support, how does
> the
> >>> community feel about making the documentation "blink only"?
> >>>
> >>> We would update the documentation to assume users are always using the
> >>> Blink planner. As the legacy planner still exists we would create a
> >>> dedicated legacy planner page for users that have not migrated for
> >> whatever
> >>> reason - likely dataset interop. On this page, we would clearly list
> the
> >>> features that are not supported by the legacy planner and any semantics
> >>> that differ from the Blink planner.
> >>>
> >>> Seth
> >>>
> >>
> >>
> >
>
>

Re: .ORC file reading from Apache Flink +SCALA

[Marta Paes Moreira]

Hi, Ajay.

*Note:* in the future, please send this type of questions to the user
mailing list instead (u...@flink.apache.org)!

Which API and Flink version are you using? The documentation/JavaDocs have
information on how to read Orc files (and other bulk-encoded formats) using
the DataStream API [1] and the Table API/SQL [2]. For the DataStream API, I
didn't find any examples using Scala, but you should be able to derive an
implementation from the snippet in this [3] Jira ticket.

If you still struggle with your implementation after referencing to that,
please provide some more details on the issue you're facing.

Marta

[1]
https://ci.apache.org/projects/flink/flink-docs-master/api/java/org/apache/flink/orc/package-summary.html
[2]
https://ci.apache.org/projects/flink/flink-docs-stable/dev/table/connectors/formats/orc.html
[3] https://issues.apache.org/jira/browse/FLINK-16646

On Sun, Sep 27, 2020 at 7:06 PM Ajay Kumar  wrote:

> Hi Team,
>
> I am struggling to read .ORC file as a source from Apache flink.
> Unfortunately there is no reach reference over internet also,
>
> Appreciate your help !
>
> Thanks in advance !
>
> Regards
> Ajay
>

Re: Apply for permission of jira contributor

[Marta Paes Moreira]

Hi, Xie.

You no longer need to request permission to contribute to Flink [1], and
can directly comment on the issue you'd like to contribute to.

Please check the contribution guide for more information on the process [2].

Marta

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-JIRA-
permissions
-changed-Only-committers-can-assign-somebody-to-a-ticket-td30695.html
[2] https://flink.apache.org/contributing/contribute-code.html

On Mon, Sep 28, 2020 at 3:05 AM Xie Billy  wrote:

> Hi Guys,
>
> I want to contribute to Apache Flink.
> Would you please give me the permission as a contributor?
> My JIRA ID is billyxie. thanks a lot.
>
>
>
> Best Regards!
> Billy xie(谢志民)
>

Re: Does Flink support such a feature currently?

[Marta Paes Moreira]

Hi, Roc.

*Note:* in the future, please send this type of questions to the user
mailing list instead (u...@flink.apache.org)!

If I understand your question correctly, this is possible using the LIKE
clause and a registered catalog. There is currently no implementation for
the MySQL JDBC catalog, but this is in the roadmap [1,2].

Once you register a catalog, you could do:

CREATE TABLE mapping_table

WITH (

  ...

 )

LIKE full_path_to_source_table;
Again, as of Flink 1.11 this only works for Postgres, not yet MySQL. I'm
copying in Bowen as he might be able to give more information on the
roadmap.

Marta

[1] https://issues.apache.org/jira/browse/FLINK-15352
[2]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-93%3A+JDBC+catalog+and+Postgres+catalog

On Tue, Sep 22, 2020 at 9:44 AM Roc Marshal  wrote:

> Hi, everyone!
>
>When using flink sql DDL to create a mysql mapping table, does
> flink support the automatic rendering of the target table schema if we put
> no column-names in `create table table_name_mapping2mysql () with (...)`?
> If this feature is not supported, is it necessary to consider improving it?
>
> Thank you.
> Best, Roc.

Re: [ANNOUNCE] New Apache Flink Committer - Niels Basjes

[Marta Paes Moreira]

Congrats, Niels!

On Mon, Sep 14, 2020 at 8:56 PM David Anderson 
wrote:

> Congratulations!
>
> --David
>
> On Mon, Sep 14, 2020 at 8:24 PM Arvid Heise  wrote:
>
> > Congrats Niels!
> >
> > On Mon, Sep 14, 2020 at 4:04 PM Benchao Li  wrote:
> >
> > > Congratulations!
> > >
> > > Xingbo Huang  于2020年9月14日周一 下午9:36写道：
> > >
> > > > Congratulations!
> > > >
> > > > Best,
> > > > Xingbo
> > > >
> > > > Dian Fu  于2020年9月14日周一 下午8:06写道：
> > > >
> > > > > Congratulations!
> > > > >
> > > > > Regards,
> > > > > Dian
> > > > >
> > > > > > 在 2020年9月14日，下午7:45，Zhu Zhu  写道：
> > > > > >
> > > > > > Congratulations!
> > > > > >
> > > > > > Thanks,
> > > > > > Zhu
> > > > > >
> > > > > > Matt Wang  于2020年9月14日周一 下午5:22写道：
> > > > > >
> > > > > >> Congratulations, Niels!
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >>
> > > > > >> Best,
> > > > > >> Matt Wang
> > > > > >>
> > > > > >>
> > > > > >> On 09/14/2020 17:02，Konstantin Knauf
> > > wrote：
> > > > > >> Congratulations!
> > > > > >>
> > > > > >> On Mon, Sep 14, 2020 at 10:51 AM tison 
> > > wrote:
> > > > > >>
> > > > > >> Congrats!
> > > > > >>
> > > > > >> Best,
> > > > > >> tison.
> > > > > >>
> > > > > >>
> > > > > >> Aljoscha Krettek  于2020年9月14日周一 下午4:38写道：
> > > > > >>
> > > > > >> Congratulations! 💐
> > > > > >>
> > > > > >> Aljoscha
> > > > > >>
> > > > > >> On 14.09.20 10:37, Robert Metzger wrote:
> > > > > >> Hi all,
> > > > > >>
> > > > > >> On behalf of the PMC, I’m very happy to announce Niels Basjes
> as a
> > > new
> > > > > >> Flink committer.
> > > > > >>
> > > > > >> Niels has been an active community member since the early days
> of
> > > > > >> Flink,
> > > > > >> with 19 commits dating back until 2015.
> > > > > >> Besides his work on the code, he has been driving initiatives on
> > > dev@
> > > > > >> list,
> > > > > >> supporting users and giving talks at conferences.
> > > > > >>
> > > > > >> Please join me in congratulating Niels for becoming a Flink
> > > committer!
> > > > > >>
> > > > > >> Best,
> > > > > >> Robert Metzger
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >>
> > > > > >> Konstantin Knauf | Head of Product
> > > > > >>
> > > > > >> +49 160 91394525
> > > > > >>
> > > > > >>
> > > > > >> Follow us @VervericaData Ververica 
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >>
> > > > > >> Join Flink Forward  - The Apache
> > Flink
> > > > > >> Conference
> > > > > >>
> > > > > >> Stream Processing | Event Driven | Real Time
> > > > > >>
> > > > > >> --
> > > > > >>
> > > > > >> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> > > > > >>
> > > > > >> --
> > > > > >> Ververica GmbH
> > > > > >> Registered at Amtsgericht Charlottenburg: HRB 158244 B
> > > > > >> Managing Directors: Yip Park Tung Jason, Jinwei (Kevin) Zhang,
> > Karl
> > > > > Anton
> > > > > >> Wehner
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Best,
> > > Benchao Li
> > >
> >
> >
> > --
> >
> > Arvid Heise | Senior Java Developer
> >
> > 
> >
> > Follow us @VervericaData
> >
> > --
> >
> > Join Flink Forward  - The Apache Flink
> > Conference
> >
> > Stream Processing | Event Driven | Real Time
> >
> > --
> >
> > Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> >
> > --
> > Ververica GmbH
> > Registered at Amtsgericht Charlottenburg: HRB 158244 B
> > Managing Directors: Timothy Alexander Steinert, Yip Park Tung Jason, Ji
> > (Toni) Cheng
> >
>

Re: Next Stateful Functions Release

[Marta Paes Moreira]

+1

The feature set also seems quite in line with user feedback, which is
always great to see.

Thanks, Igal!

On Thu, Aug 27, 2020 at 1:34 PM Robert Metzger  wrote:

> +1 to release Statefun 2.2
>
> On Tue, Aug 25, 2020 at 2:16 PM David Anderson 
> wrote:
>
> > Igal,
> >
> > The feature set you propose sounds great to me -- as a user I see
> > plenty there to get excited about. As for the feature freeze date, I
> > don't really have an informed opinion.
> >
> > David
> >
> > On Mon, Aug 24, 2020 at 10:15 AM Igal Shilman 
> wrote:
> > >
> > > Hi Flink devs,
> > >
> > > We have a few upcoming / implemented features for Stateful Functions on
> > the
> > > radar, and would like to give a heads up on what to expect for the next
> > > release:
> > >
> > > 1. Upgrade support for Flink 1.11.x. [FLINK-18812]
> > > 2. Fine grained control on remote state configuration, such as state
> TTL.
> > > [FLINK-17954]
> > > 3. New state construct for dynamic state registration [FLINK-18316]
> > > 4. Add a DataStream API to StateFun [FLINK-19001]
> > > 5. Support async handlers for the Python SDK [FLINK-18518]
> > > 6. Add more metrics around async operations and backpressure
> > [FLINK-19020]
> > > 7. Out-of-box support for common storage systems in flink-statefun
> Docker
> > > image [FLINK-19019]
> > >
> > > With these we think the project will be in a good spot for the next
> > release.
> > > What do you think about aiming at 10.9.2020 for a feature freeze for
> > > StateFun 2.2?
> > >
> > > Kind regards,
> > > Igal.
> >
>

Re: [ANNOUNCE] New PMC member: Dian Fu

[Marta Paes Moreira]

Congrats, Dian!

On Thu, Aug 27, 2020 at 11:39 AM Yuan Mei  wrote:

> Congrats!
>
> On Thu, Aug 27, 2020 at 5:38 PM Xingbo Huang  wrote:
>
>> Congratulations Dian!
>>
>> Best,
>> Xingbo
>>
>> jincheng sun  于2020年8月27日周四 下午5:24写道：
>>
>>> Hi all,
>>>
>>> On behalf of the Flink PMC, I'm happy to announce that Dian Fu is now
>>> part of the Apache Flink Project Management Committee (PMC).
>>>
>>> Dian Fu has been very active on PyFlink component, working on various
>>> important features, such as the Python UDF and Pandas integration, and
>>> keeps checking and voting for our releases, and also has successfully
>>> produced two releases(1.9.3&1.11.1) as RM, currently working as RM to push
>>> forward the release of Flink 1.12.
>>>
>>> Please join me in congratulating Dian Fu for becoming a Flink PMC Member!
>>>
>>> Best,
>>> Jincheng(on behalf of the Flink PMC)
>>>
>>

[ANNOUNCE] Introducing the GSoD 2020 Participants.

[Marta Paes Moreira]

Hi, Everyone!

I'd like to officially welcome the applicants that were selected to work
with the Flink community for this year's Google Season of Docs (GSoD)
[1]: *Kartik
Khare* and *Muhammad Haseeb Asif*!

   - Kartik [2] is a software engineer at Walmart Labs and a regular
   contributor to multiple Apache projects. He is also a prolific writer on
   Medium and has previously published on the Flink blog. Last year, he
   contributed to Apache Airflow as part of GSoD and he's currently revamping
   the Apache Pinot documentation.


   - Muhammad [3] is a dual degree master student at KTH and TU Berlin,
   focusing on distributed systems and data intensive processing (in
   particular, performance optimization of state backends). He writes
   frequently about Flink on Medium and you can catch him and his colleague
   Sruthi this Friday at Beam Summit [4]!

They will be working to improve the Table API/SQL documentation over a
3-month period, with the support of Aljoscha and Seth as mentors.

Please give them a warm welcome to the Flink developer community!

Marta

[1] https://developers.google.com/season-of-docs/docs/participants
[2] https://github.com/KKcorps
[3] https://www.linkedin.com/in/haseebasif/
[4] https://2020.beamsummit.org/sessions/nexmark-beam-flinkndb/

Re: [ANNOUNCE] New Flink Committer: David Anderson

[Marta Paes Moreira]

Congrats, David! Thanks for being the Flink Stack Overflow hawk (on top of
everything else, of course)!

Marta

On Thu, Aug 13, 2020 at 5:26 AM Roc Marshal  wrote:

>
>
>
>
>
>
> Congratulations David!
>
>
> Best,
> Roc Marshal.
>
>
>
>
>
>
>
>
>
>
>
> At 2020-08-12 15:50:47, "Robert Metzger"  wrote:
> >Hi everyone,
> >
> >On behalf of the PMC, I'm very happy to announce David Anderson as a new
> >Apache
> >Flink committer.
> >
> >David has been a Flink community member for a long time. His first commit
> >dates back to 2016, code changes mostly involve the documentation, in
> >particular with the recent contribution of Flink training materials.
> >Besides that, David has been giving numerous talks and trainings on Flink.
> >On StackOverflow, he's among the most active helping Flink users to solve
> >their problems (2nd in the all-time ranking, 1st in the last 30 days). A
> >similar level of activity can be found on the user@ mailing list.
> >
> >Please join me in congratulating David for becoming a Flink committer!
> >
> >Best,
> >Robert
>

Re: [DISCUSS] FLIP-133: Rework PyFlink Documentation

[Marta Paes Moreira]

Hi, Jincheng!

Thanks for creating this detailed FLIP, it will make a big difference in
the experience of Python developers using Flink. I'm interested in
contributing to this work, so I'll reach out to you offline!

Also, thanks for sharing some information on the adoption of PyFlink, it's
great to see that there are already production users.

Marta

On Fri, Jul 31, 2020 at 5:35 AM Xingbo Huang  wrote:

> Hi Jincheng,
>
> Thanks a lot for bringing up this discussion and the proposal.
>
> Big +1 for improving the structure of PyFlink doc.
>
> It will be very friendly to give PyFlink users a unified entrance to learn
> PyFlink documents.
>
> Best,
> Xingbo
>
> Dian Fu  于2020年7月31日周五 上午11:00写道：
>
>> Hi Jincheng,
>>
>> Thanks a lot for bringing up this discussion and the proposal. +1 to
>> improve the Python API doc.
>>
>> I have received many feedbacks from PyFlink beginners about
>> the PyFlink doc, e.g. the materials are too few, the Python doc is mixed
>> with the Java doc and it's not easy to find the docs he wants to know.
>>
>> I think it would greatly improve the user experience if we can have one
>> place which includes most knowledges PyFlink users should know.
>>
>> Regards,
>> Dian
>>
>> 在 2020年7月31日，上午10:14，jincheng sun  写道：
>>
>> Hi folks,
>>
>> Since the release of Flink 1.11, users of PyFlink have continued to grow.
>> As far as I know there are many companies have used PyFlink for data
>> analysis, operation and maintenance monitoring business has been put into
>> production(Such as 聚美优品[1](Jumei),  浙江墨芷[2] (Mozhi) etc.).  According to
>> the feedback we received, current documentation is not very friendly to
>> PyFlink users. There are two shortcomings:
>>
>> - Python related content is mixed in the Java/Scala documentation, which
>> makes it difficult for users who only focus on PyFlink to read.
>> - There is already a "Python Table API" section in the Table API document
>> to store PyFlink documents, but the number of articles is small and the
>> content is fragmented. It is difficult for beginners to learn from it.
>>
>> In addition, FLIP-130 introduced the Python DataStream API. Many
>> documents will be added for those new APIs. In order to increase the
>> readability and maintainability of the PyFlink document, Wei Zhong and me
>> have discussed offline and would like to rework it via this FLIP.
>>
>> We will rework the document around the following three objectives:
>>
>> - Add a separate section for Python API under the "Application
>> Development" section.
>> - Restructure current Python documentation to a brand new structure to
>> ensure complete content and friendly to beginners.
>> - Improve the documents shared by Python/Java/Scala to make it more
>> friendly to Python users and without affecting Java/Scala users.
>>
>> More detail can be found in the FLIP-133:
>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-133%3A+Rework+PyFlink+Documentation
>>
>> Best,
>> Jincheng
>>
>> [1] https://mp.weixin.qq.com/s/zVsBIs1ZEFe4atYUYtZpRg
>> [2] https://mp.weixin.qq.com/s/R4p_a2TWGpESBWr3pLtM2g
>>
>>
>>

Re: [ANNOUNCE] New PMC member: Piotr Nowojski

[Marta Paes Moreira]

Go Piotr! Congrats!

On Tue, Jul 7, 2020 at 7:15 AM Biao Liu  wrote:

> Congrats Piotr! Well deserved!
>
> Thanks,
> Biao /'bɪ.aʊ/
>
>
>
> On Tue, 7 Jul 2020 at 13:03, Congxian Qiu  wrote:
>
> > Congratulations Piotr!
> >
> > Best,
> > Congxian
> >
> >
> > Zhijiang  于2020年7月7日周二 下午12:25写道：
> >
> > > Congratulations Piotr!
> > >
> > > Best,
> > > Zhijiang
> > >
> > >
> > > --
> > > From:Rui Li 
> > > Send Time:2020年7月7日(星期二) 11:55
> > > To:dev 
> > > Cc:pnowojski 
> > > Subject:Re: [ANNOUNCE] New PMC member: Piotr Nowojski
> > >
> > > Congrats!
> > >
> > > On Tue, Jul 7, 2020 at 11:25 AM Yangze Guo  wrote:
> > >
> > > > Congratulations!
> > > >
> > > > Best,
> > > > Yangze Guo
> > > >
> > > > On Tue, Jul 7, 2020 at 11:01 AM Jiayi Liao 
> > > > wrote:
> > > > >
> > > > > Congratulations Piotr!
> > > > >
> > > > > Best,
> > > > > Jiayi Liao
> > > > >
> > > > > On Tue, Jul 7, 2020 at 10:54 AM Jark Wu  wrote:
> > > > >
> > > > > > Congratulations Piotr!
> > > > > >
> > > > > > Best,
> > > > > > Jark
> > > > > >
> > > > > > On Tue, 7 Jul 2020 at 10:50, Yuan Mei 
> > > wrote:
> > > > > >
> > > > > > > Congratulations, Piotr!
> > > > > > >
> > > > > > > On Tue, Jul 7, 2020 at 1:07 AM Stephan Ewen 
> > > > wrote:
> > > > > > >
> > > > > > > > Hi all!
> > > > > > > >
> > > > > > > > It is my pleasure to announce that Piotr Nowojski joined the
> > > Flink
> > > > PMC.
> > > > > > > >
> > > > > > > > Many of you may know Piotr from the work he does on the data
> > > > processing
> > > > > > > > runtime and the network stack, from the mailing list, or the
> > > > release
> > > > > > > > manager work.
> > > > > > > >
> > > > > > > > Congrats, Piotr!
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Stephan
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> > >
> > > --
> > > Best regards!
> > > Rui Li
> > >
> > >
> >
>

Re: [VOTE] Release 1.11.0, release candidate #3

[Marta Paes Moreira]

Thanks, Zhijiang!

The PR for the release announcement blogpost is now available in [1]. Any
feedback or comments are appreciated!

[1] https://github.com/apache/flink-web/pull/352

On Wed, Jun 24, 2020 at 5:03 PM Zhijiang 
wrote:

> Hi everyone,
>
> This RC3 vote is re-launched for fixing the tag issue ([ANNOUNCE] ->
> [VOTE]) in email title and adjusting the vote period (72 hours -> 48 hours)
>  based on the latest considerations.
>
> Please review and vote on the release candidate #3 for the version 1.11.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint 2DA85B93244FDFA19A6244500653C0A2CEA00D0E [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.11.0-rc3" [5],
> * Marta is also preparing a pull request for the announcement blog post in
> the works, and will update this voting thread with a link to the pull
> request shortly afterwards.
>
> The vote will be open for at least 48 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Note we would probably have the next RC4 based on the latest feedbacks to
> cover mainly cosmetic/API changes, but most other testing efforts should be
> forwardable.
>
>
> Thanks,
> Release Manager
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12346364
> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.11.0-rc3/
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1376/
> [5] https://github.com/apache/flink/releases/tag/release-1.11.0-rc3

Re: [DISCUSS] Re-renaming "Flink Master" back to JobManager

[Marta Paes Moreira]

+1

I've found the term Flink Master a tad bit confusing myself, in the past,
as it's not used consistently throughout the documentation (as you mention).

Thanks for following up on this, Aljoscha!

On Wed, Jun 17, 2020 at 5:16 PM Robert Metzger  wrote:

> Thanks a lot for looking into this!
>
> +1 to your proposal
>
> On Wed, Jun 17, 2020 at 10:55 AM David Anderson 
> wrote:
>
> > Aljoscha,
> >
> > I think this is a step in the right direction.
> >
> > In some cases it may be difficult to talk concretely about the
> > differences between different deployment models (e.g., comparing a k8s
> > per-job cluster to a YARN-based session cluster, which is something I
> > typically present during training) without giving names to the internal
> > components. I'm not convinced we can completely avoid mentioning the
> > JobMaster (and Dispatcher and ResourceManagers) in some (rare) contexts
> --
> > but I don't see this as an argument against the proposed change.
> >
> > David
> >
> > On Mon, Jun 15, 2020 at 2:32 PM Konstantin Knauf 
> > wrote:
> >
> > > Hi Aljoscha,
> > >
> > > sounds good to me. Let’s also make sure we don’t refer to the JobMaster
> > as
> > > Jobmanager anywhere then (code, config).
> > >
> > > I am not sure we can avoid mentioning the Flink ResourceManagers in
> user
> > > facing docs completely. For JobMaster and Dispatcher this seems doable.
> > >
> > > Best,
> > >
> > > Konstantin
> > >
> > > On Mon 15. Jun 2020 at 12:56, Aljoscha Krettek 
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > This came to my mind because of the master/slave discussion in [1]
> and
> > > > the larger discussions about inequality/civil rights happening right
> > now
> > > > in the world. I think for this reason alone we should use a name that
> > > > does not include "master".
> > > >
> > > > We could rename it back to JobManager, which was the name mostly used
> > > > before 2019. Since the beginning of Flink, TaskManager was the term
> > used
> > > > for the worker component/node and JobManager was the term used for
> the
> > > > orchestrating component/node.
> > > >
> > > > Currently our glossary [2] defines these terms (paraphrased by me):
> > > >
> > > >   - "Flink Master": it's the orchestrating component that consists of
> > > > resource manager, dispatcher, and JobManager
> > > >
> > > >   - JobManager: it's the thing that manages a single job and runs as
> > > > part of a "Flink Master"
> > > >
> > > >   - TaskManager: it's the worker process
> > > >
> > > > Prior to the introduction of the glossary the definition of
> JobManager
> > > > would have been:
> > > >
> > > >   - It's the orchestrating component that manages execution of jobs
> and
> > > > schedules work on TaskManagers.
> > > >
> > > > Quite some parts in the code and documentation/configuration options
> > > > still use that older meaning of JobManager. Newer parts of the
> > > > documentation use "Flink Master" instead.
> > > >
> > > > I'm proposing to go back to calling the orchestrating component
> > > > JobManager, which would mean that we have to touch up the
> documentation
> > > > to remove mentions of "Flink Master". I'm also proposing not to
> mention
> > > > the internal components such as resource manager and dispatcher in
> the
> > > > glossary because there are transparent to users.
> > > >
> > > > I'm proposing to go back to JobManager instead of an alternative name
> > > > also because switching to yet another name would mean many more
> changes
> > > > to code/documentation/peoples minds.
> > > >
> > > > What do you all think?
> > > >
> > > > Best,
> > > > Aljoscha
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/FLINK-18209
> > > > [2]
> > > >
> > > >
> > >
> >
> https://ci.apache.org/projects/flink/flink-docs-master/concepts/glossary.html
> > > >
> > > --
> > >
> > > Konstantin Knauf
> > >
> > > https://twitter.com/snntrable
> > >
> > > https://github.com/knaufk
> > >
> >
>

Re: [ANNOUNCE] Yu Li is now part of the Flink PMC

[Marta Paes Moreira]

Awesome! Congratulations, Yu!

On Thu, Jun 18, 2020 at 9:16 AM Zhu Zhu  wrote:

> Congratulations!
>
> Thanks,
> Zhu Zhu
>
> Guowei Ma  于2020年6月18日周四 上午10:41写道：
>
> > Congratulations , Yu!
> > Best,
> > Guowei
> >
> >
> > Yang Wang  于2020年6月18日周四 上午10:36写道：
> >
> > > Congratulations , Yu!
> > >
> > > Best,
> > > Yang
> > >
> > > Piotr Nowojski  于2020年6月17日周三 下午9:21写道：
> > >
> > > > Congratulations :)
> > > >
> > > > > On 17 Jun 2020, at 14:53, Yun Tang  wrote:
> > > > >
> > > > > Congratulations , Yu! well deserved.
> > > > >
> > > > > Best
> > > > > Yun Tang
> > > > > 
> > > > > From: Yu Li 
> > > > > Sent: Wednesday, June 17, 2020 20:03
> > > > > To: dev 
> > > > > Subject: Re: [ANNOUNCE] Yu Li is now part of the Flink PMC
> > > > >
> > > > > Thanks everyone! Really happy to work in such a great and
> encouraging
> > > > > community!
> > > > >
> > > > > Best Regards,
> > > > > Yu
> > > > >
> > > > >
> > > > > On Wed, 17 Jun 2020 at 19:59, Congxian Qiu  >
> > > > wrote:
> > > > >
> > > > >> Congratulations Yu !
> > > > >> Best,
> > > > >> Congxian
> > > > >>
> > > > >>
> > > > >> Thomas Weise  于2020年6月17日周三 下午6:23写道：
> > > > >>
> > > > >>> Congratulations!
> > > > >>>
> > > > >>>
> > > > >>> On Wed, Jun 17, 2020, 2:59 AM Fabian Hueske 
> > > wrote:
> > > > >>>
> > > >  Congrats Yu!
> > > > 
> > > >  Cheers, Fabian
> > > > 
> > > >  Am Mi., 17. Juni 2020 um 10:20 Uhr schrieb Till Rohrmann <
> > > >  trohrm...@apache.org>:
> > > > 
> > > > > Congratulations Yu!
> > > > >
> > > > > Cheers,
> > > > > Till
> > > > >
> > > > > On Wed, Jun 17, 2020 at 7:53 AM Jingsong Li <
> > > jingsongl...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Congratulations Yu, well deserved!
> > > > >>
> > > > >> Best,
> > > > >> Jingsong
> > > > >>
> > > > >> On Wed, Jun 17, 2020 at 1:42 PM Yuan Mei <
> > yuanmei.w...@gmail.com>
> > > >  wrote:
> > > > >>
> > > > >>> Congrats, Yu!
> > > > >>>
> > > > >>> GXGX & well deserved!!
> > > > >>>
> > > > >>> Best Regards,
> > > > >>>
> > > > >>> Yuan
> > > > >>>
> > > > >>> On Wed, Jun 17, 2020 at 9:15 AM jincheng sun <
> > > >  sunjincheng...@gmail.com>
> > > > >>> wrote:
> > > > >>>
> > > >  Hi all,
> > > > 
> > > >  On behalf of the Flink PMC, I'm happy to announce that Yu Li
> > is
> > > > >> now
> > > >  part of the Apache Flink Project Management Committee (PMC).
> > > > 
> > > >  Yu Li has been very active on Flink's Statebackend
> component,
> > > > >>> working
> > > > > on
> > > >  various improvements, for example the RocksDB memory
> > management
> > > > >> for
> > > > > 1.10.
> > > >  and keeps checking and voting for our releases, and also has
> > > > > successfully
> > > >  produced two releases(1.10.0&1.10.1) as RM.
> > > > 
> > > >  Congratulations & Welcome Yu Li!
> > > > 
> > > >  Best,
> > > >  Jincheng (on behalf of the Flink PMC)
> > > > 
> > > > >>>
> > > > >>
> > > > >> --
> > > > >> Best, Jingsong Lee
> > > > >>
> > > > >
> > > > 
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: Interested in contributing to Apache Flink

[Marta Paes Moreira]

Hi, Vivin!

Thanks for your interest in participating in Google Season of Docs (GSoD)
and contributing to Apache Flink! We're glad that you enjoyed working with
Flink before, and that it motivated you to now apply to GSoD.

Regarding what you can work on, there are no strict requirements since
there is a lot of work to be done in the Table API / SQL documentation.
Here is a bit more detail about each part of our idea proposal [1]:

*"Restructure the Table API & SQL Documentation*

Right now the Table / SQL documentation is very technical and dry to read.
It is more like a technical specification than documentation that a new
user could read. This project is to take the existing content and
rewrite/reorganize it to make what the community already has more
approachable.

*Extend the Table API & SQL Documentation*

This is to add brand new content. This could be tutorials and walkthroughs
to help onboard new users or expanding an under-documented section such as
Hive interop."

Please remember to follow the GSoD application process [2] and timeline
[3]. Let us know if you have any further questions!

Marta

[1] https://flink.apache.org/news/2020/05/04/season-of-docs.html
[2]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints
[3] https://developers.google.com/season-of-docs/docs/timeline


On Mon, Jun 15, 2020 at 10:13 AM Vivin Peris  wrote:

> Respected Sir
>
> I am currently a final year undergrad student at National Institute of
> Technology Surathkal, India.
>
> I have extensively worked on Apache Flink in my previous internship where I
> had to create a database of billions of IPs in the world along with data
> associated with it.
> The power of Flink is just unbelievable and helped me do work which would
> take months in just a matter of two days.
>
> With this background, I am deeply interested in applying to your esteemed
> organization under Google Season of Developers. Since I am new to technical
> writing, I am willing to work hard.
>
> I would like to know what I can work on so that I can equip myself for this
> task.
>
> Thank you for your time and consideration
>
> Sincerely
> Vivin
>

Re: Regarding GSOD opportunity at Apache Flink

[Marta Paes Moreira]

Hi, Aditya.

I left a reply in your previous thread!

Thanks,

Marta

On Wed, Jun 10, 2020 at 9:06 PM Aditya Kumar Hurkat 4-Yr B.Tech. Mining
Engg., IIT (BHU) Varanasi 
wrote:

> Hello!
>
> I am Aditya Hurkat a Junior Undergraduate at IIT-BHU, India.
> I always have admired the work of open source communities, and now there is
> an opportunity for me to work for such communities through GSOD.
> I needed help regarding what criteria is being used for selecting students
> for GSOD program at Apache Flink.
>
>
>
> Best
>
> Aditya
>
> *आदित्य कुमार हुरकट*
>
> *खनन अभियांत्रिकी विभाग*
>
> *भारतीय प्रौद्योगिकी संस्थान (काशी हिन्दू विश्वविधालय)*
>
> *वाराणासी, उत्तरप्रदेश -221005*
>
> *भारत*
> *Aditya Kumar Hurkat*
> *Department of Mining Engineering*
> *Indian Institute of Technology (Banaras Hindu University)*
>
> *Varanasi, Uttar Pradesh -221005*
> *India*
>
> This message is intended for the addressee only and may contain
> confidential or privileged information. The communication is the property
> of IIT (BHU) and its affiliates and may contain copyright material or
> intellectual property of IIT(BHU) and/or any of its related entities or of
> third parties. If you are not the intended recipient of the communication
> or have received the communication in error, please notify the sender
> immediately, return the communication (in entirety) and delete the
> communication (in entirety and copies included) from your records and
> systems. Unauthorized use, disclosure or copying of this communication or
> any part thereof is strictly prohibited and may be unlawful.
>

Re: Regarding GSOD opportunity at Apache Flink

[Marta Paes Moreira]

Hey, Aditya!

Thanks for reaching out and for being interested in contributing to open
source (and Flink, in particular!) as part of Google Season of Docs (GSoD)!

We will follow GSoD's guidelines [1] to evaluate incoming projects. Does
this clarify your question?

Let me know if there is anything else we can help you with!

[1] https://developers.google.com/season-of-docs/docs/project-selection

On Wed, Jun 10, 2020 at 2:48 PM Aditya Kumar Hurkat 4-Yr B.Tech. Mining
Engg., IIT (BHU) Varanasi 
wrote:

> Hello!
>
> I am Aditya Hurkat a Junior Undergraduate at IIT-BHU, India.
> I always have admired the work of open source communities, and now there is
> an opportunity for me to work for such communities through GSOD.
> I needed help regarding what criteria is being used for selecting students
> for GSOD program at Apache Flink.
>
>
>
> Best
>
> Aditya
>
> *आदित्य कुमार हुरकट*
>
> *खनन अभियांत्रिकी विभाग*
>
> *भारतीय प्रौद्योगिकी संस्थान (काशी हिन्दू विश्वविधालय)*
>
> *वाराणासी, उत्तरप्रदेश -221005*
>
> *भारत*
> *Aditya Kumar Hurkat*
> *Department of Mining Engineering*
> *Indian Institute of Technology (Banaras Hindu University)*
>
> *Varanasi, Uttar Pradesh -221005*
> *India*
>
> This message is intended for the addressee only and may contain
> confidential or privileged information. The communication is the property
> of IIT (BHU) and its affiliates and may contain copyright material or
> intellectual property of IIT(BHU) and/or any of its related entities or of
> third parties. If you are not the intended recipient of the communication
> or have received the communication in error, please notify the sender
> immediately, return the communication (in entirety) and delete the
> communication (in entirety and copies included) from your records and
> systems. Unauthorized use, disclosure or copying of this communication or
> any part thereof is strictly prohibited and may be unlawful.
>

Re: Interested in applying as a technical writer

[Marta Paes Moreira]

Great! Are you familiar with the Google Season of Docs application process?

I'm sharing the link in case you need more information, just in case [1].
You can submit your ideas until *July 9th*.

Thanks again for your interest, Deepak! Let me know if there is anything
else we can do to help.

Marta

[1]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints

On Wed, Jun 10, 2020 at 2:25 PM Deepak Vohra  wrote:

>
> Marta,
>
> Thanks for directing me to the project  Improve the Table API & SQL
> Documentation. I would be interested in Improve the Table API & SQL
> Documentation. These are more aligned with my background in relational
> databases  as I have used almost all commonly used relational databases.
> Moreover, the API is in Java, and I am Oracle certified Java Programmer.
>
> Deepak
> On Tuesday, June 9, 2020, 10:33:56 p.m. PDT, Marta Paes Moreira <
> ma...@ververica.com> wrote:
>
>
> Hi, Deepak!
>
> In reply to your email (below): the project proposal [1] focuses on the
> Table API / SQL, so I'm afraid that working on the DataSet API
> documentation is out of scope for our participation in Google Season of
> Docs.
>
> Is there anything within the scope of the proposal that you'd like to work
> on instead?
>
> Otherwise, you can open a JIRA [2] ticket and propose these improvements
> as a regular community contribution. Just for reference, the DataSet API is
> going to be deprecated in the future in favour of a unified batch/streaming
> API [3].
>
> Let me know if you have any questions.
>
> Marta
>
> [1] https://flink.apache.org/news/2020/05/04/season-of-docs.html
> [2] https://issues.apache.org/jira/projects/FLINK/summary
> [3] https://flink.apache.org/roadmap.html#batch-and-streaming-unification
>
> "Thanks Marta,
>
> One of the lacking features I noticed is that several example programs are
> missing for Java and Scala as in Data Sources section on page Apache
> Flink 1.10 Documentation: Flink DataSet API Programming Guide
> <https://ci.apache.org/projects/flink/flink-docs-release-1.10/dev/batch/>
>
> Apache Flink 1.10 Documentation: Flink DataSet API Programming Guide
>
> <https://ci.apache.org/projects/flink/flink-docs-release-1.10/dev/batch/>
> I could develop the example programs among other additions.
>
> regards,
> Deepak"
>
> On Mon, Jun 8, 2020 at 6:56 PM Marta Paes Moreira 
> wrote:
>
> Hi, Deepak!
>
> At the time, I didn't notice you were potentially not subscribed to the
> mailing list, so you may not have gotten my reply. Just resending it in
> case you didn't get it!
>
> "
> date: May 15, 2020, 2:53 PMHi, Deepak.
>
> Thanks for the introduction — it's cool to see that you're interested in
> contributing to Flink as part of GSoD!
>
> We're looking forward to receiving your application! Let us know if you
> have any questions, in the meantime.
>
> Marta
> "
>
> On Fri, May 15, 2020 at 2:53 PM Marta Paes Moreira 
> wrote:
>
> Hi, Deepak.
>
> Thanks for the introduction — it's cool to see that you're interested in
> contributing to Flink as part of GSoD!
>
> We're looking forward to receiving your application! Let us know if you
> have any questions, in the meantime.
>
> Marta
>
> On Thu, May 14, 2020 at 11:35 PM Deepak Vohra 
> wrote:
>
> I am interested in applying as a technical writer to the Apache Flink
> project in Google Season of Docs. In the project exploration phase I would
> like to introduce myself as a potential applicant (when the application
> opens). I have experience using several data processing frameworks and have
> published dozens of articles and a few books on the same. Some books on
> similar topics :
>  1.Practical Hadoop Ecosystemhttps://
> www.amazon.com/gp/product/B01M0NAHU3/ref=dbs_a_def_rwt_hsch_vapi_tkin_p1_i5
> 2. Apache HBase Primerhttps://
> www.amazon.com/gp/product/B01MTOSTAB/ref=dbs_a_def_rwt_bibl_vppi_i1
> I have also published 5 other books on Docker and Kubernetes; Kubernetes
> being a commonly used deployment platform for Apache Flink.
> regards,Deepak
>
>

Re: Interested in applying as a technical writer

[Marta Paes Moreira]

Hi, Deepak!

In reply to your email (below): the project proposal [1] focuses on the
Table API / SQL, so I'm afraid that working on the DataSet API
documentation is out of scope for our participation in Google Season of
Docs.

Is there anything within the scope of the proposal that you'd like to work
on instead?

Otherwise, you can open a JIRA [2] ticket and propose these improvements as
a regular community contribution. Just for reference, the DataSet API is
going to be deprecated in the future in favour of a unified batch/streaming
API [3].

Let me know if you have any questions.

Marta

[1] https://flink.apache.org/news/2020/05/04/season-of-docs.html
[2] https://issues.apache.org/jira/projects/FLINK/summary
[3] https://flink.apache.org/roadmap.html#batch-and-streaming-unification

"Thanks Marta,

One of the lacking features I noticed is that several example programs are
missing for Java and Scala as in Data Sources section on page Apache Flink
1.10 Documentation: Flink DataSet API Programming Guide
<https://ci.apache.org/projects/flink/flink-docs-release-1.10/dev/batch/>

Apache Flink 1.10 Documentation: Flink DataSet API Programming Guide

<https://ci.apache.org/projects/flink/flink-docs-release-1.10/dev/batch/>
I could develop the example programs among other additions.

regards,
Deepak"

On Mon, Jun 8, 2020 at 6:56 PM Marta Paes Moreira 
wrote:

> Hi, Deepak!
>
> At the time, I didn't notice you were potentially not subscribed to the
> mailing list, so you may not have gotten my reply. Just resending it in
> case you didn't get it!
>
> "
> date: May 15, 2020, 2:53 PMHi, Deepak.
>
> Thanks for the introduction — it's cool to see that you're interested in
> contributing to Flink as part of GSoD!
>
> We're looking forward to receiving your application! Let us know if you
> have any questions, in the meantime.
>
> Marta
> "
>
> On Fri, May 15, 2020 at 2:53 PM Marta Paes Moreira 
> wrote:
>
>> Hi, Deepak.
>>
>> Thanks for the introduction — it's cool to see that you're interested in
>> contributing to Flink as part of GSoD!
>>
>> We're looking forward to receiving your application! Let us know if you
>> have any questions, in the meantime.
>>
>> Marta
>>
>> On Thu, May 14, 2020 at 11:35 PM Deepak Vohra 
>> wrote:
>>
>>> I am interested in applying as a technical writer to the Apache Flink
>>> project in Google Season of Docs. In the project exploration phase I would
>>> like to introduce myself as a potential applicant (when the application
>>> opens). I have experience using several data processing frameworks and have
>>> published dozens of articles and a few books on the same. Some books on
>>> similar topics :
>>>  1.Practical Hadoop Ecosystemhttps://
>>> www.amazon.com/gp/product/B01M0NAHU3/ref=dbs_a_def_rwt_hsch_vapi_tkin_p1_i5
>>> 2. Apache HBase Primerhttps://
>>> www.amazon.com/gp/product/B01MTOSTAB/ref=dbs_a_def_rwt_bibl_vppi_i1
>>> I have also published 5 other books on Docker and Kubernetes; Kubernetes
>>> being a commonly used deployment platform for Apache Flink.
>>> regards,Deepak
>>
>>

Re: Interest registration for Documentation task relating Table API & SQL

[Marta Paes Moreira]

There seems to be some thread confusion here. @Deepak, I'll reply to you in
the original thread ("Interested in applying as a technical writer").

Sorry, Abdul!

On Wed, Jun 10, 2020 at 1:59 AM Deepak Vohra  wrote:

> Thanks Marta,
>
> One of the lacking features I noticed is that several example programs are
> missing for Java and Scala as in Data Sources section on page Apache
> Flink 1.10 Documentation: Flink DataSet API Programming Guide
> <https://ci.apache.org/projects/flink/flink-docs-release-1.10/dev/batch/>
>
> Apache Flink 1.10 Documentation: Flink DataSet API Programming Guide
>
> <https://ci.apache.org/projects/flink/flink-docs-release-1.10/dev/batch/>
> I could develop the example programs among other additions.
>
> regards,
> Deepak
>
>
>
>
> On Saturday, June 6, 2020, 01:16:14 a.m. PDT, Marta Paes Moreira <
> ma...@ververica.com> wrote:
>
>
> Hi, Abdul.
>
> Thank you for reaching out and for your interest in Google Season of Docs
> (GSoD)!
>
> We really appreciate it that you took the time to walk us through your
> experience, as well as your previous contributions to open source. Even
> though we are accepting applications from people with any kind of
> background, being familiar with Flink and similar projects is definitely
> an advantage — so, we highly encourage you to apply! You can learn more
> about the application process of GSoD in [1,2].
>
> Let us know if you have any questions, we're happy to help!
>
> Thanks,
>
> Marta
>
> [1] https://developers.google.com/season-of-docs/docs/timeline
> [2]
>
> https://developers.google.com/season-of-docs/docs/tech-writer-application-hints
>
> On Thu, Jun 4, 2020 at 7:46 PM abdul basit  wrote:
>
> > Hello Aljoscha Krettek and Seth Wiesman,
> >
> > I am Abdul Basit, An enthusiast Data Science and Engineering
> professional.
> > I am currently doing my Industrial PhD focussing on developing predictive
> > maintenance solutions with the help of Big Data, Cloud and AI tools. My
> PhD
> > is in collaboration with Eit Digital, City University of London and Bosch
> > group.
> >
> > I have previously done two masters in Data Engineering, Machine learning
> > and have 3 years of industrial experience in these areas. My aim and
> > interest is to bridge the gap between researchers and industry by helping
> > researchers to adapt to the modern tools in the domain of Data and AI.
> For
> > example, introducing them to tools for building data preparation
> pipelines
> > with Apache Airflow,Apache Spark, Kafka and others.
> >
> > I have contributed <https://github.com/apache/airflow/pull/6007> to
>
> > Apache Airflow by implementing a AWS Glue plugin for developing better
> data
> > and ML pipelines. While working on Data Engineering tasks as part of my
> > projects, I became interested in Apache flink and after about it
> use-cases,
> > I really started to appreciate it and tried to do some hands-on by
> > replacing Spark Streaming with Flink.
> >
> > Having worked on a few Big data processing frameworks, I believe that
> > flink has a lot of potential that has yet to be appreciated by the big
> data
> > community. Documentation and guides available with the official project
> > plays a very crucial role in increasing the adaptability of the project.
> > So, I started to search for the option to contribute to this awesome
> > project and fortunately found the documentation Improvement proposal
> > "FLIP-60: Restructure the Table API & SQL documentation"  and "Flip
> > 12369 Extend the Table API & SQL Documentation" , which is part of google
> > season of code.
> >
> > I will be very happy to contribute towards any of these two tasks of
> > restructuring and extending Table APi and SQL Documentation. I have read
> > the detailed descriptions of these projects and they align perfectly with
> > my experience. My previous exposure to Apache spark and Kafka will help
> me
> > to adopt more efficiently to the task. I will look forward to your
> opinion
> > on my profile before the official application to google season of Docs. I
> > have attached my CV for the reference.
> >
> > --
> > Thanks
> >
> > Regards,
> > Abdul Basit
> >
> >
>

Re: [DISCUSS] Add Japanese translation of the flink.apache.org website

[Marta Paes Moreira]

I had a second look at the PR and maybe it'd be important to clarify the
scope.

It seems to only target the website and, if that's the case, then
synchronization might be less of an issue as the core of the website is
pretty static. I'm not sure how useful it is to have a translated website
without any other kind of support (e.g. mailing list, documentation) in the
same language, but the contributor might be able to shed some light on this.

Just wanted to amend my original reply as it was pretty blindsided by the
previous comments. It'd be worth understanding the end goal of the
contribution first.

Thanks,

Marta

On Tue, Jun 9, 2020 at 2:22 PM Congxian Qiu  wrote:

> Hi
>
> Thanks for bringing this up, Robert.
>
> I agree we may need to investigate better translation/synchronization tools
> again.
>
> I'll share some experience when translating the documentation or reviewing
> the translation.
> 1. Translate documentation using the current procedure needs a lot of
> resources to keep the translated version fresh, I'm glad that we have so
> many contributors who want to translate the documentation to Chinese.
> 2. The documentation may out of sync between the English version and the
> translated version, this needs the reviewer to know about Flink and the
> English version doc very well(especially when the documentation has been
> restructured)
>
> Best,
> Congxian
>
>
> Jark Wu  于2020年6月9日周二 下午6:02写道：
>
> > I agree with Dawid and others' opinions.
> >
> > We may not have enough resources to maintain more languages.
> > Maybe it's time to investigate better translation/synchronization tools
> > again.
> >
> > I want to share some background about the current translation process. In
> > the initial proposal of Chinese translation FLIP-35 [1],
> > we have considered Docusaurus/Crowdin as the localization tool, but it
> > seems that Crowdin doesn't fit well with Jekyll (Liquid codes).
> > But it's been a year and a half, maybe it's time to re-investigate them
> or
> > other tools.
> >
> > Here is the list of how other ASF projects are dealing translation of
> what
> > I know:
> > - Apache Pulsar uses Crowdin:
> https://github.com/apache/pulsar-translation
> > - Apache Kylin: the similar way of Flink:
> > https://github.com/apache/kylin/tree/document/website
> > - Apache RocketMQ: a separate repository, synchronize manually and
> > periodically: https://github.com/apache/rocketmq/tree/master/docs/cn
> >
> > Here is the list of localization tool of what I know:
> > - Docusaurus: https://docusaurus.io/
> > - Crowdin: https://crowdin.com/
> > - GitLocalize: https://gitlocalize.com/
> >
> > Best,
> > Jark
> >
> > On Tue, 9 Jun 2020 at 16:24, Marta Paes Moreira 
> > wrote:
> >
> > > Thanks for bringing this PR to our attention, Robert!
> > >
> > > Like Dawid and Xintong, I'm concerned that adding a new language will
> > make
> > > it unbearable to ensure docs synchronization. Best-effort maintenance
> of
> > > non-english docs may also result in a bad documentation experience for
> > > users, and this is something that we should be especially careful about
> > in
> > > locations where Flink adoption might still be in an early phase, IMO.
> At
> > > the same time, I understand that having a japanese translation would
> > > probably be very helpful for Japanese-speaking users and help with
> Flink
> > > adoption in Japan.
> > >
> > > I see this happening for other up-and-coming locations (e.g.
> > > Spanish-speaking countries) in the future, so in order to be able to
> > accept
> > > these contributions I'm also of the opinion that we first need an
> > efficient
> > > synchronization tool. Maybe it would be worth investigating how other
> ASF
> > > projects are dealing with this.
> > >
> > > Marta
> > >
> > > On Mon, Jun 8, 2020 at 11:46 AM Xintong Song 
> > > wrote:
> > >
> > > > I think Dawid has a good point. With or without another new language,
> > > > I'm +1 for trying to have a better tooling/process for synchronizing
> > doc
> > > > changes.
> > > >
> > > > Currently, it is not only hard for people who want to modify the
> > English
> > > > docs, but also for people who try to update the translated copies
> > > > accordingly. I'm currently working on updating the Chinese
> translations
> > > for
> > > > 

Re: [ANNOUNCE] New Flink Committer: Benchao Li

[Marta Paes Moreira]

Congrats, Benchao!

On Tue, Jun 9, 2020 at 11:41 AM Till Rohrmann  wrote:

> Congratulations!
>
> Cheers,
> Till
>
> On Tue, Jun 9, 2020 at 11:19 AM Yang Wang  wrote:
>
> > Congratulations!
> >
> > Best,
> > Yang
> >
> > Yu Li  于2020年6月9日周二 下午5:11写道：
> >
> > > Congratulations, Benchao!
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Tue, 9 Jun 2020 at 17:05, Yuan Mei  wrote:
> > >
> > > > Congrats!
> > > >
> > > > On Tue, Jun 9, 2020 at 2:10 PM Jark Wu  wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > On behalf of the PMC, I'm very happy to announce Benchao Li as a
> new
> > > > Apache
> > > > > Flink committer.
> > > > >
> > > > > Benchao started contributing to Flink since late 2018. He is very
> > > active
> > > > in
> > > > > Flink SQL component,
> > > > > and has also participated in many discussions, bug fixes. Over the
> > past
> > > > few
> > > > > months, he helped tremendously in answering user questions in the
> > > mailing
> > > > > list.
> > > > >
> > > > > Please join me in congratulating Benchao for becoming a Flink
> > > committer!
> > > > >
> > > > > Thanks,
> > > > > Jark
> > > > >
> > > >
> > >
> >
>

[jira] [Created] (FLINK-18209) Replace "charged" words in the Flink codebase.

[Marta Paes Moreira (Jira)]

Marta Paes Moreira created FLINK-18209:
--

 Summary: Replace "charged" words in the Flink codebase.
 Key: FLINK-18209
 URL: https://issues.apache.org/jira/browse/FLINK-18209
 Project: Flink
  Issue Type: Task
Reporter: Marta Paes Moreira


The Flink codebase still makes use of "charged" words that are considered 
outdated and have a negative connotation. In particular, this is the number of 
occurrences of such words:


"Slave": 229
 
"Whitelist": 23
 
"Blacklist": 28
 
I'd like to propose that we [rethink the use of these 
words|[https://lethargy.org/~jesus/writes/a-guide-to-nomenclature-selection/]] 
and consider existing alternatives that other open source projects are also 
adopting. Replacing all occurrences is non-trivial in many cases and may 
involve breaking-changes, though, so one idea would be to break this effort 
down into different phases that can be tackled over time, depending on the 
impact of the required changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Add Japanese translation of the flink.apache.org website

[Marta Paes Moreira]

Thanks for bringing this PR to our attention, Robert!

Like Dawid and Xintong, I'm concerned that adding a new language will make
it unbearable to ensure docs synchronization. Best-effort maintenance of
non-english docs may also result in a bad documentation experience for
users, and this is something that we should be especially careful about in
locations where Flink adoption might still be in an early phase, IMO. At
the same time, I understand that having a japanese translation would
probably be very helpful for Japanese-speaking users and help with Flink
adoption in Japan.

I see this happening for other up-and-coming locations (e.g.
Spanish-speaking countries) in the future, so in order to be able to accept
these contributions I'm also of the opinion that we first need an efficient
synchronization tool. Maybe it would be worth investigating how other ASF
projects are dealing with this.

Marta

On Mon, Jun 8, 2020 at 11:46 AM Xintong Song  wrote:

> I think Dawid has a good point. With or without another new language,
> I'm +1 for trying to have a better tooling/process for synchronizing doc
> changes.
>
> Currently, it is not only hard for people who want to modify the English
> docs, but also for people who try to update the translated copies
> accordingly. I'm currently working on updating the Chinese translations for
> the memory configuration documents, and I found it very hard to identify
> the parts that need updates. The English docs are reorganized, contents are
> moved across pages, and also small pieces of details are modified. It is
> not always possible for people who work on the English docs to locate the
> right place in the translations where the updated contents should be
> pasted.
>
> My two cents on the potential approach. We might label the translation with
> the commit id of the original doc where they are in synchronization, and
> automatically display a warning on the translation if an out-of-sync is
> detected.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Mon, Jun 8, 2020 at 4:30 PM Dawid Wysakowicz 
> wrote:
>
> > I don't have a well defined opinion on adding new language. However, one
> > thing that I'd like to bring up to the attention on that occasion is it
> > is already quite cumbersome to update two versions of the docs.
> > Especially when we add new sections or change smaller parts of an
> > existing document. Right now if I add three sections in an English
> > version I have three additional places in the Chinese documents where I
> > need to paste that. With additional language it doubles, making it 6
> > places where I have to manually paste the added parts.
> >
> > I'd be way more welcoming for adding a new language if we had a better
> > tooling/process for synchronizing changes across different languages. Or
> > if we agree the translations are best effort documents and we do not
> > update them when changing the English documents.
> >
> > Best,
> >
> > Dawid
> >
> > On 08/06/2020 09:44, Robert Metzger wrote:
> > > Hi all,
> > >
> > > we've received a pull request on flink-web.git for adding a Japanese
> > > translation of the Flink website:
> > > https://github.com/apache/flink-web/pull/346
> > >
> > > Before we accept this PR, I believe we should have a discussion about
> it.
> > >
> > > *Relevance*: Looking at Google analytics, our users are coming from
> China
> > > (1.), US (2.), India (3.), Germany (4.), Japan (5.).
> > > I'd say that is high enough to consider a Japanese translation.
> > >
> > > *Reviewing*: I'm not aware of any committer who speaks Japanese. How
> > would
> > > we review this?
> > > The contributor is offering to open follow-up pull requests, which I
> > > believe is fine to bootstrap. Ideally we'll be able to attract more
> > > contributors over time.
> > >
> > > In my opinion, if we find one or two reviewers, I would give this a
> try.
> > >
> > > What do you think?
> > >
> > > Best,
> > > Robert
> > >
> >
> >
>

Re: Google Season of Docs Contribution

[Marta Paes Moreira]

Hi, Aman!

Thanks for reaching out and for your interest in Google Season of Docs
(GSoD)! To participate, you have to first submit an application with your
project proposal(s) [1]. Just to shed a bit more light on what we are
looking for:

*"Restructure the Table API & SQL Documentation*



*Right now the Table / SQL documentation is very technical and dry to read.
It is more like a technical specification than documentation that a new
user could read. This project is to take the existing content and
rewrite/reorganize it to make what the community already has more
approachable.*
*Extend the Table API & SQL Documentation*

*This is to add brand new content. This could be tutorials and walkthroughs
to help onboard new users or expanding an under-documented section such as
Hive interoperability."*

The applications are open as of tomorrow (June 9th) and you can learn more
about the process of applying to GSoD in [2,3].

Let me know if you have any other questions!

Thanks,

Marta

[1]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints#project_proposal

[2] https://developers.google.com/season-of-docs/docs/timeline
[3]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints

On Mon, Jun 8, 2020 at 9:27 AM Aman Singal  wrote:

> Respected Sir,
>
> I am Aman Singal, I am a 2nd Year undergraduate student. I really would
> like to contribute in your esteemed organization in writing documentation.
> I have read and understood the requirement of the project "Extend the Table
> API & SQL Documentation"
>
> I request you to please share the details and guide me the path to get
> started.
>
> Yours Sincerely
> Aman Singal
>

Re: Interested in applying as a technical writer

[Marta Paes Moreira]

Hi, Deepak!

At the time, I didn't notice you were potentially not subscribed to the
mailing list, so you may not have gotten my reply. Just resending it in
case you didn't get it!

"
date: May 15, 2020, 2:53 PMHi, Deepak.

Thanks for the introduction — it's cool to see that you're interested in
contributing to Flink as part of GSoD!

We're looking forward to receiving your application! Let us know if you
have any questions, in the meantime.

Marta
"

On Fri, May 15, 2020 at 2:53 PM Marta Paes Moreira 
wrote:

> Hi, Deepak.
>
> Thanks for the introduction — it's cool to see that you're interested in
> contributing to Flink as part of GSoD!
>
> We're looking forward to receiving your application! Let us know if you
> have any questions, in the meantime.
>
> Marta
>
> On Thu, May 14, 2020 at 11:35 PM Deepak Vohra 
> wrote:
>
>> I am interested in applying as a technical writer to the Apache Flink
>> project in Google Season of Docs. In the project exploration phase I would
>> like to introduce myself as a potential applicant (when the application
>> opens). I have experience using several data processing frameworks and have
>> published dozens of articles and a few books on the same. Some books on
>> similar topics :
>>  1.Practical Hadoop Ecosystemhttps://
>> www.amazon.com/gp/product/B01M0NAHU3/ref=dbs_a_def_rwt_hsch_vapi_tkin_p1_i5
>> 2. Apache HBase Primerhttps://
>> www.amazon.com/gp/product/B01MTOSTAB/ref=dbs_a_def_rwt_bibl_vppi_i1
>> I have also published 5 other books on Docker and Kubernetes; Kubernetes
>> being a commonly used deployment platform for Apache Flink.
>> regards,Deepak
>
>

Re: Interest registration for Documentation task relating Table API & SQL

[Marta Paes Moreira]

Hi, Abdul.

Thank you for reaching out and for your interest in Google Season of Docs
(GSoD)!

We really appreciate it that you took the time to walk us through your
experience, as well as your previous contributions to open source. Even
though we are accepting applications from people with any kind of
background, being familiar with Flink and similar projects is definitely
an advantage — so, we highly encourage you to apply! You can learn more
about the application process of GSoD in [1,2].

Let us know if you have any questions, we're happy to help!

Thanks,

Marta

[1] https://developers.google.com/season-of-docs/docs/timeline
[2]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints

On Thu, Jun 4, 2020 at 7:46 PM abdul basit  wrote:

> Hello Aljoscha Krettek and Seth Wiesman,
>
> I am Abdul Basit, An enthusiast Data Science and Engineering professional.
> I am currently doing my Industrial PhD focussing on developing predictive
> maintenance solutions with the help of Big Data, Cloud and AI tools. My PhD
> is in collaboration with Eit Digital, City University of London and Bosch
> group.
>
> I have previously done two masters in Data Engineering, Machine learning
> and have 3 years of industrial experience in these areas. My aim and
> interest is to bridge the gap between researchers and industry by helping
> researchers to adapt to the modern tools in the domain of Data and AI. For
> example, introducing them to tools for building data preparation pipelines
> with Apache Airflow,Apache Spark, Kafka and others.
>
> I have contributed  to
> Apache Airflow by implementing a AWS Glue plugin for developing better data
> and ML pipelines. While working on Data Engineering tasks as part of my
> projects, I became interested in Apache flink and after about it use-cases,
> I really started to appreciate it and tried to do some hands-on by
> replacing Spark Streaming with Flink.
>
> Having worked on a few Big data processing frameworks, I believe that
> flink has a lot of potential that has yet to be appreciated by the big data
> community. Documentation and guides available with the official project
> plays a very crucial role in increasing the adaptability of the project.
> So, I started to search for the option to contribute to this awesome
> project and fortunately found the documentation Improvement proposal
> "FLIP-60: Restructure the Table API & SQL documentation"  and "Flip
> 12369 Extend the Table API & SQL Documentation" , which is part of google
> season of code.
>
> I will be very happy to contribute towards any of these two tasks of
> restructuring and extending Table APi and SQL Documentation. I have read
> the detailed descriptions of these projects and they align perfectly with
> my experience. My previous exposure to Apache spark and Kafka will help me
> to adopt more efficiently to the task. I will look forward to your opinion
> on my profile before the official application to google season of Docs. I
> have attached my CV for the reference.
>
> --
> Thanks
>
> Regards,
> Abdul Basit
>
>

Re: [ANNOUNCE] New Apache Flink Committer - Xintong Song

[Marta Paes Moreira]

Congratulations, Tony! Great job!

On Fri, Jun 5, 2020 at 8:00 AM Yang Wang  wrote:

> Congratulations, Xintong.
> Well deserved.
>
> Best,
> Yang
>
> Weihua Hu  于2020年6月5日周五 下午1:57写道：
>
> > Congratulations!
> >
> > Best
> > Weihua Hu
> >
> > > 2020年6月5日 13:50，Xingbo Huang  写道：
> > >
> > > Congratulations, Xintong.
> > >
> > > Best,
> > > Xingbo
> > >
> > > Jiayi Liao  于2020年6月5日周五 下午1:49写道：
> > >
> > >> Congratulations!
> > >>
> > >> Best,
> > >> Jiayi Liao
> > >>
> > >> On Fri, Jun 5, 2020 at 1:48 PM Biao Liu  wrote:
> > >>
> > >>> Congrats!
> > >>>
> > >>> Thanks,
> > >>> Biao /'bɪ.aʊ/
> > >>>
> > >>>
> > >>>
> > >>> On Fri, 5 Jun 2020 at 13:32, Thomas Weise  wrote:
> > >>>
> >  Congratulations!
> > 
> > 
> >  On Thu, Jun 4, 2020, 10:17 PM Yuan Mei 
> > wrote:
> > 
> > > Congrats, Xintong!
> > >
> > > On Fri, Jun 5, 2020 at 12:45 PM Becket Qin 
> > >>> wrote:
> > >
> > >> Hi all,
> > >>
> > >> On behalf of the PMC, I’m very happy to announce Xintong Song as a
> > >>> new
> > >> Flink committer.
> > >>
> > >> Xintong started to contribute to Flink about two years ago and has
> > >>> been
> > >> active since. His major work is in Flink resource management, and
> > >>> have
> > > also
> > >> participated in discussions, bug fixes and answering questions.
> > >>
> > >> Please join me in congratulating Xintong for becoming a Flink
> >  committer!
> > >>
> > >> Thanks,
> > >>
> > >> Jiangjie (Becket) Qin
> > >>
> > >
> > 
> > >>>
> > >>
> >
> >
>

Re: Subscription mail

[Marta Paes Moreira]

You're right, Tison. I forgot to include his e-mail address, so thanks for
doing that (seems like we had a case of concurrency here, too!).

Thanks!

Marta

On Fri, May 29, 2020 at 9:44 AM tison  wrote:

> Hi,
>
> I'm not very sure but IIRC if someone didn't subscribe to this mailing list
> yet, he could not receive mail from the list.
>
> Best,
> tison.
>
>
> 夏帅  于2020年5月29日周五 下午2:44写道：
>
> > send email to dev-subscr...@flink.apache.org
> >
> >
> > --
> > 发件人：kartheek annamaneni 
> > 发送时间：2020年5月29日(星期五) 14:38
> > 收件人：dev 
> > 主 题：Subscription mail
> >
> > Hi,
> >   How can I subscribe to this?
> >
> >
>

Re: Subscription mail

[Marta Paes Moreira]

Hi, Kartheek.

To subscribe, please send an e-mail to dev-subscr...@flink.apache.org. If
you have any questions, you can find more detailed instructions in [1].

Marta

[1]
https://flink.apache.org/community.html#how-to-subscribe-to-a-mailing-list

On Fri, 29 May 2020 at 08:38, kartheek annamaneni <
kartheekannamanen...@gmail.com> wrote:

> Hi,
>   How can I subscribe to this?
>

Fwd: Season of Docs - Ex-participant Intro

[Marta Paes Moreira]

Hi again, Kartik!

Our project idea is pretty open-ended — there really is a lot of work to do
in the Table API / SQL documentation, so we're not being picky about what
people choose to work on. Regarding timelines on our side, I think FLIP-60
and other documentation improvement proposals will be tackled more ad-hoc
style and not so much like a continuous project, as there isn't *one*
person dedicated to just focusing on that.

If you're looking for a bit more concrete points, Seth did a good summary
in a previous thread:

*"Restructure the Table API & SQL Documentation*



*Right now the Table / SQL documentation is very technical and dry to read.
It is more like a technical specification than documentation that a new
user could read. This project is to take the existing content and
rewrite/reorganize it to make what the community already has more
approachable.*
*Extend the Table API & SQL Documentation*

*This is to add brand new content. This could be tutorials and walkthroughs
to help onboard new users or expanding an under-documented section such as
Hive interop."*

Feel free to ask for a review of your project proposal once you've put it
together, if you feel like you need it! And sorry again for the broken
e-mail chain.

Marta

-- Forwarded message -
From: Kartik Khare 
Date: Wed, May 27, 2020 at 7:48 PM
Subject: Re: Season of Docs - Ex-participant Intro
To: Marta Paes Moreira 


Hi Seth and Marta,
No issues at all.
I was looking forward to getting started with the proposal document for
GSoD.
I wanted to know what are the expectations from the document. I am assuming
you must be looking for the timelines for various stages of the project.
Other than that, the proposals already have a detailed structure of what
the documentation should look like but we can have a discussion to check if
there is scope for moving some of the sections.

Regards,
Kartk

On Wed, May 27, 2020 at 11:09 PM Marta Paes Moreira 
wrote:

> Hi, Kartik!
>
> Sorry that you didn't get our replies to your self-presentation. You can
> find them below!
>
> Let me know if you have any questions.
>
> Marta
>
> -- Forwarded message -
> From: Marta Paes Moreira 
> Date: Thu, May 14, 2020 at 8:37 AM
> Subject: Re: Season of Docs - Ex-participant Intro
> To: dev 
> Cc: 
>
>
> Hey, Kartik!
>
> Thanks for reaching out and sharing your experience on GSoD last year.
>
> Let us know if you have any questions about the project that we can help
> with before the applications phase kicks off!
>
> Marta
>
> On Wed, May 13, 2020 at 11:30 PM Seth Wiesman  wrote:
>
>> Hey Kartik,
>>
>> Nice to connect, I am one of the GSoD mentors, along with Aljoscha in cc.
>> Happy to see you're interested in working with the community.
>>
>> Seth
>>
>> On Wed, May 13, 2020 at 4:10 PM Kartik Khare 
>> wrote:
>>
>> > Hi,
>> > This is Kartik. I an genuinely interested in working with your
>> organisation
>> > for Google season of Docs. I work as data engineer @ walmart labs but
>> also
>> > write a lot of blogs on distributed systems on
>> > https://medium.com/@kharekartik.
>> >
>> > I contributed one on flink's website as well:
>> >
>> >
>> https://flink.apache.org/news/2020/02/07/a-guide-for-unit-testing-in-apache-flink.html
>> >
>> > I participated as technical writer last year as well for Apache Airflow.
>> > You can check my project and journey here:
>> >
>> >
>> https://airflow.apache.org/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/
>> >
>> > Let's keep in touch.
>> >
>> >
>> > Regards,
>> > Kartik Khare
>> >
>>
>

Fwd: Season of Docs - Ex-participant Intro

[Marta Paes Moreira]

Hi, Kartik!

Sorry that you didn't get our replies to your self-presentation. You can
find them below!

Let me know if you have any questions.

Marta

-- Forwarded message -
From: Marta Paes Moreira 
Date: Thu, May 14, 2020 at 8:37 AM
Subject: Re: Season of Docs - Ex-participant Intro
To: dev 
Cc: 


Hey, Kartik!

Thanks for reaching out and sharing your experience on GSoD last year.

Let us know if you have any questions about the project that we can help
with before the applications phase kicks off!

Marta

On Wed, May 13, 2020 at 11:30 PM Seth Wiesman  wrote:

> Hey Kartik,
>
> Nice to connect, I am one of the GSoD mentors, along with Aljoscha in cc.
> Happy to see you're interested in working with the community.
>
> Seth
>
> On Wed, May 13, 2020 at 4:10 PM Kartik Khare 
> wrote:
>
> > Hi,
> > This is Kartik. I an genuinely interested in working with your
> organisation
> > for Google season of Docs. I work as data engineer @ walmart labs but
> also
> > write a lot of blogs on distributed systems on
> > https://medium.com/@kharekartik.
> >
> > I contributed one on flink's website as well:
> >
> >
> https://flink.apache.org/news/2020/02/07/a-guide-for-unit-testing-in-apache-flink.html
> >
> > I participated as technical writer last year as well for Apache Airflow.
> > You can check my project and journey here:
> >
> >
> https://airflow.apache.org/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/
> >
> > Let's keep in touch.
> >
> >
> > Regards,
> > Kartik Khare
> >
>

Re: [DISCUSS] Releasing Stateful Functions 2.1.0 soon?

[Marta Paes Moreira]

+1 for more frequent releases with a shorter (but feedback-informed)
feature set.

Thanks, Gordon (and Igal)!

Marta

On Thu, 21 May 2020 at 03:44, Yu Li  wrote:

> +1, it makes a lot of sense for stateful functions to evolve faster.
>
> Best Regards,
> Yu
>
>
> On Wed, 20 May 2020 at 23:36, Zhijiang  .invalid>
> wrote:
>
> > I also like this idea, considering stateful functions flexible enough to
> > have a faster release cycle. +1 from my side.
> >
> > Best,
> > Zhijiang
> >
> >
> > --
> > From:Seth Wiesman 
> > Send Time:2020年5月20日(星期三) 21:45
> > To:dev 
> > Subject:Re: [DISCUSS] Releasing Stateful Functions 2.1.0 soon?
> >
> > +1 for a fast release cycle
> >
> > Seth
> >
> > On Wed, May 20, 2020 at 8:43 AM Robert Metzger 
> > wrote:
> >
> > > I like the idea of releasing Statefun more frequently to have faster
> > > feedback cycles!
> > >
> > > No objections for releasing 2.1.0 from my side.
> > >
> > > On Wed, May 20, 2020 at 2:22 PM Tzu-Li (Gordon) Tai <
> tzuli...@apache.org
> > >
> > > wrote:
> > >
> > > > Hi devs,
> > > >
> > > > Since Stateful Functions 2.0 was released early April,
> > > > we've been getting some good feedback from various channels,
> > > > including the Flink mailing lists, JIRA issues, as well as Stack
> > Overflow
> > > > questions.
> > > >
> > > > Some of the discussions have actually translated into new features
> > > > currently being implemented into the project, such as:
> > > >
> > > >- State TTL for the state primitives in Stateful Functions (for
> both
> > > >embedded/remote functions)
> > > >- Transport for remote functions via UNIX domain sockets, which
> > would
> > > be
> > > >useful when remote functions are co-located with Flink StateFun
> > > workers
> > > >(i.e. the "sidecar" deployment mode)
> > > >
> > > >
> > > > Besides that, some critical shortcomings have already been addressed
> > > since
> > > > the last release:
> > > >
> > > >- After upgrading to Flink 1.10.1, failure recovery in Stateful
> > > >Functions now works properly with the new scheduler.
> > > >- Support for concurrent checkpoints
> > > >
> > > >
> > > > With these ongoing threads, while it's only been just short of 2
> months
> > > > since the last release,
> > > > we (Igal Shilman and I) have been thinking about aiming to already
> > start
> > > > the next feature release (2.1.0) soon.
> > > > This is relatively shorter than the release cycle of what the
> community
> > > is
> > > > used to in Flink (usually 3 months at least),
> > > > but we think with the StateFun project in its early phases, having
> > > smaller
> > > > and more frequent feature releases could potentially help drive user
> > > > adoption.
> > > >
> > > > So, what do you think about setting feature freeze for StateFun 2.1.0
> > by
> > > > next Wednesday (May 27th)?
> > > > Of course, whether or not to actually have another feature release
> > > already
> > > > is still an open discussion - if you prefer a richer feature release
> > with
> > > > more features included besides the ones listed above, please do
> > comment!
> > > >
> > > > Cheers,
> > > > Gordon
> > > >
> > >
> >
> >
>

Fwd: Google Season of Document

[Marta Paes Moreira]

Forwarding Seth's reply, which was only sent to the mailing list (you can
only see these if you are subscribed [1]).

[1] https://flink.apache.org/community.html#mailing-lists

-- Forwarded message -
From: Seth Wiesman 
Date: Tue, May 19, 2020 at 4:32 PM
Subject: Re: Google Season of Document
To: dev 


Hi Hossam,

Please apply! We look forward to reviewing your application. Let us know if
you have any questions.

Seth

On Tue, May 19, 2020 at 8:09 AM Hossam Elsafty  wrote:

> Dear aljoscha and sjwiesman,
>
> I am Hossam Elsafty a graduated from the Faculty of Engineering Computer
> and System Department. As one of my academic courses, I have finished
> Technical Reports Writing.
>
> Regarding my previous experience, I have done two internships as a
> Software Engineer including one in Valeo Egypt and the other in the Saudi
> Arabia Ministry of National Gaurd. Also, I am certified from Udacity for
> finishing the Machine Learning Engineer Nanodegree program.
>
> Currently, I am working as a Big Data Engineer for 1 year at Ejada System
> in Saudi Arabia, I worked in many projects for the Saudi Ministry of
> Finance using Cloudera Hadoop ecosystems.
>
> I am sending this mail to ask if I can apply to your organization in
> Google Season of Document.
> I am looking forward to your reply.
>
> Regards,
> Hossam Fawzy Elsafty
>
> Computer and System Department 2019
> Faculty of Engineering ,Alexandria university
>
>

Re: Season Of Docs Discussion

[Marta Paes Moreira]

Hi, Amardeep!

Thanks for reaching out and for your interest in working with the Flink
community during Google Season of Docs!

It's great to hear that you have an idea for your proposal already — I'd be
happy to hear more about it.

I'll contact you in a separate thread!

Marta

On Mon, May 18, 2020 at 9:08 AM Amardeep Singh 
wrote:

> Hello,
> I am currently an engineering student with the University Of Toronto and
> have worked extensively with companies in the past for both engineering and
> technical documentation concepts.
> I've gone through the project ideas for Apache Flink and would be extremely
> privileged to have an opportunity to work with the team. To better
> understand the requirements and details, I would like to schedule a call to
> provide a glimpse of my own ideas and possible additions that can be made.
> I am attaching my Linkedin profile and Github link for your reference.
> Hoping to hear back soon.
> https://www.linkedin.com/in/amardeep-s-70a471a3/
> https://github.com/AmDeep
> Amardeep Singh.
>

Re: Google Season of Docs

[Marta Paes Moreira]

Hi, Amr!

You can certainly apply for Google Season of Docs with the Flink project.
All you have to do is have a look at our project ideas [1], think about
what you'd be interested in working on and submit your application once the
application phase opens (June 9th) [2].

Let me know if there is anything else I can help you with in the process!

Marta

[1] https://flink.apache.org/news/2020/05/04/season-of-docs.html
[2]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints

On Sat, May 16, 2020 at 8:32 AM Amr Maghraby  wrote:

> Dear Apace Flink,
> My name is Amr Maghraby, I am a new graduate from AAST college got the
> first rank on my class with CGPA 3.92 and joined the international
> competition in the US called ROV got the second worldwide and last summer I
> have involved in Google Summer of code 2019 and did good work also, I
> participated in problem-solving competitions ACM ACPC and Hash Code. I was
> asking if I could apply for GSOD?
> Waiting for your reply.
> Thanks,
> Amr Maghraby
>

Re: regarding Google Season of Docs

[Marta Paes Moreira]

Hi, Yuvraj!

Thanks for your interest in contributing to Flink during Google Season of
Docs!

You can start by reading FLIP-60 [1] and thinking about what areas of the
documentation you'd like to focus on. There is a lot of work to be done, so
there is some flexibility for you to choose topics that are in line with
your knowledge or interests. If after that you're still unsure, I can also
suggest some areas of the Table API / SQL docs that could be a good fit for
newcomers to the project.

Then, you can submit your application once the application phase opens
(June 9th) [2].

Let me know if this is what you were looking for!

[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405685
[2]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints

On Sat, May 16, 2020 at 8:32 AM Yuvraj Manral 
wrote:

> Respected sir/mam,
>
> I came around the projects proposed by Apache Flink for Season of Docs
> 2020.
> I am a newbie to organisation but really liked the ideas of projects and
> would love to start contributing and prepare my proposal for Season of
> Docs.
>
> Please guide me through. Where should I start and then proceed ?
> Thanking you in anticipation
>
> Yuvraj Manral 
> RSVP
>

Re: Interested In Google Season of Docs!

[Marta Paes Moreira]

Hi, Roopal.

Thanks for reaching out, we're glad to see that you're interested in giving
the Flink docs a try!

To participate in Google Season of Docs (GSoD), you'll have to submit an
application once the application period opens (June 9th). Because FLIP-60
is very broad, the first step would be to think about what parts of it
you'd like to focus on — or, what you'd like to have as a project proposal
[1].

You can find more information about the whole process of participating in
GSoD in [2].

Let me know if I can help you with anything else or if you need support
with choosing your focus areas.

Marta

[1]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints#project_proposal
[2]
https://developers.google.com/season-of-docs/docs/tech-writer-application-hints

On Sat, May 16, 2020 at 8:32 AM Roopal Jain  wrote:

> Hello Flink Dev Community!
>
> I am interested in participating in Google Season of Docs for Apache Flink.
> I went through the FLIP-60 detailed proposal and thought this is something
> I could do well. I am currently working as a software engineer and have a
> B.E in Computer Engineering from one of India's reputed engineering
> colleges. I have prior open-source contribution with mentoring for Google
> Summer of Code and Google Code-In.
> I have prior work experience on Apache Spark and a good grasp on SQL, Java,
> and Python.
> Please guide me more on how to get started?
>
> Thanks & Regards,
> Roopal Jain
>

Re: [PROPOSAL] Google Season of Docs 2020.

[Marta Paes Moreira]

Thanks, Robert!

I made the wrong assumption that most people would be familiar with how
mailing lists work and should have been clearer in the announcement.

On Sat, May 16, 2020 at 8:35 AM Robert Metzger  wrote:

> FYI: I'm a moderator of the dev@ list, and we've received about 5 emails
> from applicants that were not subscribed to the list.
> Initially, I rejected their messages, asking them to subscribe and send the
> email again. This has not happened from any of them.
> That's why I accepted new applicant messages now. However, this means that
> they won't receive email responses if we just reply to the list.
>
> tl:dr: Please use "Reply to all" and make sure the applicant's email
> address is included when responding to any of those applications. Thanks :)
>
> On Tue, May 12, 2020 at 11:28 AM Till Rohrmann 
> wrote:
>
> > This is great newst :-) Thanks Marta for driving this effort!
> >
> > On Mon, May 11, 2020 at 4:22 PM Sivaprasanna 
> > wrote:
> >
> > > Awesome. Great job.
> > >
> > > On Mon, 11 May 2020 at 7:22 PM, Seth Wiesman 
> > wrote:
> > >
> > > > Thank you for putting this together Marta!
> > > >
> > > > On Mon, May 11, 2020 at 8:35 AM Fabian Hueske 
> > wrote:
> > > >
> > > > > Thanks Marta and congratulations!
> > > > >
> > > > > Am Mo., 11. Mai 2020 um 14:55 Uhr schrieb Robert Metzger <
> > > > > rmetz...@apache.org>:
> > > > >
> > > > > > Awesome :)
> > > > > > Thanks a lot for driving this Marta!
> > > > > >
> > > > > > Nice to see Flink (by virtue of having Apache as part of the
> name)
> > so
> > > > > high
> > > > > > on the list, with other good open source projects :)
> > > > > >
> > > > > >
> > > > > > On Mon, May 11, 2020 at 2:18 PM Marta Paes Moreira <
> > > > ma...@ververica.com>
> > > > > > wrote:
> > > > > >
> > > > > > > I'm happy to announce that we were *accepted* into this year's
> > > Google
> > > > > > > Season of Docs!
> > > > > > >
> > > > > > > The list of projects was published today [1]. The next step is
> > for
> > > > > > > technical writers to reach out (May 11th-June 8th) and apply
> > (June
> > > > > > 9th-July
> > > > > > > 9th).
> > > > > > >
> > > > > > > Thanks again to everyone involved! I'm really looking forward
> to
> > > > > kicking
> > > > > > > off the project in September.
> > > > > > >
> > > > > > > [1]
> > > https://developers.google.com/season-of-docs/docs/participants/
> > > > > > >
> > > > > > > Marta
> > > > > > >
> > > > > > > On Thu, Apr 30, 2020 at 5:14 PM Marta Paes Moreira <
> > > > > ma...@ververica.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > The application to Season of Docs 2020 is close to being
> > > finalized.
> > > > > > I've
> > > > > > > > created a PR with the application announcement for the Flink
> > blog
> > > > [1]
> > > > > > (as
> > > > > > > > required by Google OSS).
> > > > > > > >
> > > > > > > > Thanks a lot to everyone who pitched in — and special thanks
> to
> > > > > > Aljoscha
> > > > > > > > and Seth for volunteering as mentors!
> > > > > > > >
> > > > > > > > I'll send an update to this thread once the results are out
> > (May
> > > > > 11th).
> > > > > > > >
> > > > > > > > [1] https://github.com/apache/flink-web/pull/332
> > > > > > > >
> > > > > > > > On Mon, Apr 27, 2020 at 9:28 PM Seth Wiesman <
> > > sjwies...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Hi Marta,
> > > > > > > >>
> > > > > > > >> I think this is a great idea, I'd be happy to help m

Re: Interested in applying as a technical writer

[Marta Paes Moreira]

Hi, Deepak.

Thanks for the introduction — it's cool to see that you're interested in
contributing to Flink as part of GSoD!

We're looking forward to receiving your application! Let us know if you
have any questions, in the meantime.

Marta

On Thu, May 14, 2020 at 11:35 PM Deepak Vohra 
wrote:

> I am interested in applying as a technical writer to the Apache Flink
> project in Google Season of Docs. In the project exploration phase I would
> like to introduce myself as a potential applicant (when the application
> opens). I have experience using several data processing frameworks and have
> published dozens of articles and a few books on the same. Some books on
> similar topics :
>  1.Practical Hadoop Ecosystemhttps://
> www.amazon.com/gp/product/B01M0NAHU3/ref=dbs_a_def_rwt_hsch_vapi_tkin_p1_i5
> 2. Apache HBase Primerhttps://
> www.amazon.com/gp/product/B01MTOSTAB/ref=dbs_a_def_rwt_bibl_vppi_i1
> I have also published 5 other books on Docker and Kubernetes; Kubernetes
> being a commonly used deployment platform for Apache Flink.
> regards,Deepak

Re: Season of Docs - Ex-participant Intro

[Marta Paes Moreira]

Hey, Kartik!

Thanks for reaching out and sharing your experience on GSoD last year.

Let us know if you have any questions about the project that we can help
with before the applications phase kicks off!

Marta

On Wed, May 13, 2020 at 11:30 PM Seth Wiesman  wrote:

> Hey Kartik,
>
> Nice to connect, I am one of the GSoD mentors, along with Aljoscha in cc.
> Happy to see you're interested in working with the community.
>
> Seth
>
> On Wed, May 13, 2020 at 4:10 PM Kartik Khare 
> wrote:
>
> > Hi,
> > This is Kartik. I an genuinely interested in working with your
> organisation
> > for Google season of Docs. I work as data engineer @ walmart labs but
> also
> > write a lot of blogs on distributed systems on
> > https://medium.com/@kharekartik.
> >
> > I contributed one on flink's website as well:
> >
> >
> https://flink.apache.org/news/2020/02/07/a-guide-for-unit-testing-in-apache-flink.html
> >
> > I participated as technical writer last year as well for Apache Airflow.
> > You can check my project and journey here:
> >
> >
> https://airflow.apache.org/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/
> >
> > Let's keep in touch.
> >
> >
> > Regards,
> > Kartik Khare
> >
>

Re: [PROPOSAL] Google Season of Docs 2020.

[Marta Paes Moreira]

I'm happy to announce that we were *accepted* into this year's Google
Season of Docs!

The list of projects was published today [1]. The next step is for
technical writers to reach out (May 11th-June 8th) and apply (June 9th-July
9th).

Thanks again to everyone involved! I'm really looking forward to kicking
off the project in September.

[1] https://developers.google.com/season-of-docs/docs/participants/

Marta

On Thu, Apr 30, 2020 at 5:14 PM Marta Paes Moreira 
wrote:

> The application to Season of Docs 2020 is close to being finalized. I've
> created a PR with the application announcement for the Flink blog [1] (as
> required by Google OSS).
>
> Thanks a lot to everyone who pitched in — and special thanks to Aljoscha
> and Seth for volunteering as mentors!
>
> I'll send an update to this thread once the results are out (May 11th).
>
> [1] https://github.com/apache/flink-web/pull/332
>
> On Mon, Apr 27, 2020 at 9:28 PM Seth Wiesman  wrote:
>
>> Hi Marta,
>>
>> I think this is a great idea, I'd be happy to help mentor a table
>> documentation project.
>>
>> Seth
>>
>> On Thu, Apr 23, 2020 at 8:38 AM Marta Paes Moreira 
>> wrote:
>>
>> > Thanks for the feedback!
>> >
>> > So far, the projects on the table are:
>> >
>> >1. Improving the Table API/SQL documentation.
>> >2. Improving the documentation about Deployments.
>> >3. Restructuring and standardizing the documentation about
>> Connectors.
>> >4. Finishing the Chinese translation.
>> >
>> > I think 2. would require a lot of technical knowledge about Flink, which
>> > might not be a good fit for GSoD (as discussed last year).
>> >
>> > As for mentors, we have:
>> >
>> >- Aljoscha (Table API/SQL)
>> >- Till (Deployments)
>> >- Stephan also said he'd be happy to participate as a mentor if
>> needed.
>> >
>> > For the translation project, I'm pulling in the people involved in last
>> > year's thread (Jark and Jincheng), as we would need two chinese-speaking
>> > mentors.
>> >
>> > I'll follow up with a draft proposal early next week, once we reach a
>> > consensus and have enough mentors (2 per project). Thanks again!
>> >
>> > Marta
>> >
>> >
>> > On Fri, Apr 17, 2020 at 2:53 PM Till Rohrmann 
>> > wrote:
>> >
>> > > Thanks for driving this effort Marta.
>> > >
>> > > I'd be up for mentoring improvements for the deployment section as
>> > > described in FLIP-42.
>> > >
>> > > Cheers,
>> > > Till
>> > >
>> > > On Fri, Apr 17, 2020 at 11:20 AM Aljoscha Krettek <
>> aljos...@apache.org>
>> > > wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > first, excellent that you're driving this, Marta!
>> > > >
>> > > > By now I have made quite some progress on the FLIP-42 restructuring
>> so
>> > > > that is not a good effort for someone to join now. Plus there is
>> also
>> > > > [1], which is about incorporating the existing Flink Training
>> material
>> > > > into the concepts section of the Flink doc.
>> > > >
>> > > > What I think would be very good is working on the Table API/SQL
>> > > > documentation [2]. We don't necessarily have to take the FLIP as a
>> > basis
>> > > > but we can, or we can start from a blank slate. I think the current
>> > > > structure as well as the content is sub-optimal (not good, really).
>> It
>> > > > would be ideal to have someone get to now the system and then write
>> > > > documentation for that part of Flink that has both good structure
>> and
>> > > > content and nicely guides new users.
>> > > >
>> > > > I would be very happy to mentor that effort.
>> > > >
>> > > > Best,
>> > > > Aljoscha
>> > > >
>> > > > [1]
>> > > >
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/rea9cbfffd9a1c0ca6f78f7e8c8497d81f32ed4a7b9e7a05d59f3b2e9%40%3Cdev.flink.apache.org%3E
>> > > >
>> > > > [2]
>> > > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405685
>> > > >

Re: [DISCUSS] Add a material web page under "https://flink.apache.org/"

[Marta Paes Moreira]

Hi, Yuan!

Thanks for starting this discussion! It would be really good to make those
resources more prominent in the Flink website somehow.

You can find an example close to the idea you're bringing up in [1]. My
concern is that placing all resources in a page can be hard to maintain and
a bit overwhelming. For users, it also ends up being hard to pinpoint what
they are looking for if there is too much material.

Rather than trying to maintain such a page, I think it could be valuable to
rethink the "Use Cases" section of the website and incorporate some
relevant materials in association with the right context (e.g. industry,
use case), then point users to a different place where they can find more
(e.g. the Flink Forward playlist/Slideshare or other dedicated Flink
channel).

For blogposts, what we usually do is reach out to the authors of
blogposts that are relevant to the community, but posted elsewhere, and ask
to submit them to the Flink blog as well. Could this also be an option for
the Chinese version of the blog? As far as I see, for now it's just a
mirror of the English blog.

Marta

[1] https://cwiki.apache.org/confluence/display/FLINK/Powered+by+Flink /
https://cwiki.apache.org/confluence/display/FLINK/Various+Presentations

On Mon, May 11, 2020 at 9:11 AM Yuan Mei  wrote:

> Hey folks,
>
> I am looking for a home to put and organize materials (mostly in Chinese)
> altogether for easier reference or search in the future.
>
> Those materials mainly include:
> - video records for live broadcasting of Flink related content.  For
> example, the set of selected Flink Forward talks reinterpreted and
> broadcasted in Chinese.
> - regular meet up topics, minutes, and PPTs. Meet-ups are held twice every
> month on average.
> - write-ups/blogs to share user experiences e.t.c.
>
> Currently, those materials are published through the official Flink WeChat
> account. The WeChat public account is a good way to “publish” information,
> but very difficult to search or organize afterwards. Personally, I find
> those materials are particularly helpful to users/developers not very
> familiar with Flink, me, as an example. Hence finding a place easy-to-find
> such materials is very important.
>
> There are several options we can adopt, but specifically, these materials
> are non-commercial stuff and purely for promoting the Flink community, so
> better not be tagged with any commercial trademarks.
>
> I was wondering how the English communities organize such materials? Can we
> simply put them under https://flink.apache.org/  as a subcategory? like
> https://flink.apache.org/cn
>
> Any suggestions are welcome. Thanks ahead!
>
> Best
>
> Yuan
>

Re: [DISCUSS] Update our Roadmap

[Marta Paes Moreira]

I agree with Till — this would make more sense somewhere during the
kick-off of the release cycle.


On Tue, May 5, 2020 at 4:44 PM Till Rohrmann  wrote:

> I don't think that a post-release step makes sense since the release
> manager of release X won't necessarily be involved in the high level
> planning of the release X+1.
>
> Cheers,
> Till
>
> On Tue, May 5, 2020 at 2:01 PM Robert Metzger  wrote:
>
> > Making the release managers responsible for keeping the roadmap up to
> date
> > sounds like a good idea to me!
> >
> > We could add this to the "Creating a Flink Release" Wiki page as a
> > post-release step.
> >
> > On Tue, May 5, 2020 at 10:15 AM Marta Paes Moreira 
> > wrote:
> >
> > > Thanks for bringing this up, Robert.
> > >
> > > More than updating the roadmap, it would be valuable to discuss how to
> > make
> > > this update systematic. I took care of the last update back in
> September
> > > and - to be honest - the effort for someone who is not involved in
> > release
> > > planning (or at least for me) feels unnecessarily high.
> > >
> > > One way to ensure that the roadmap is kept fresh could be to make the
> > > update part of the release kick-off (for example, as part of the
> > > responsibilities of the release managers).
> > >
> > > What do you think?
> > >
> > > Marta
> > >
> > > On Mon, May 4, 2020 at 10:35 PM Robert Metzger 
> > > wrote:
> > >
> > > > Hey all,
> > > > The roadmap has been updated last in September 2019. There is quite a
> > bit
> > > > of outdated information on that page.
> > > >
> > > > Is there a volunteer who wants to create a first draft for an updated
> > > > version?
> > > >
> > > > On Mon, Aug 19, 2019 at 12:14 PM Robert Metzger  >
> > > > wrote:
> > > >
> > > > > Nice, thanks! Looking forward to the PR
> > > > >
> > > > > On Mon, Aug 19, 2019 at 11:08 AM Marta Paes Moreira <
> > > ma...@ververica.com
> > > > >
> > > > > wrote:
> > > > >
> > > > >> Hey, Robert.
> > > > >>
> > > > >> Updating the roadmap is something I can work on (and also have on
> my
> > > > >> radar,
> > > > >> moving forward). Already had a quick word with Stephan and he's
> > > > available
> > > > >> to provide support, if needed.
> > > > >>
> > > > >> Marta
> > > > >>
> > > > >> On Sun, Aug 18, 2019 at 4:46 PM Stephan Ewen 
> > > wrote:
> > > > >>
> > > > >> > I could help with that.
> > > > >> >
> > > > >> > On Fri, Aug 16, 2019 at 2:36 PM Robert Metzger <
> > rmetz...@apache.org
> > > >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Flink 1.9 is feature freezed and almost released.
> > > > >> > > I guess it makes sense to update the roadmap on the website
> > again.
> > > > >> > >
> > > > >> > > Who feels like having a good overview of what's coming up?
> > > > >> > >
> > > > >> > > On Tue, May 7, 2019 at 4:33 PM Fabian Hueske <
> fhue...@gmail.com
> > >
> > > > >> wrote:
> > > > >> > >
> > > > >> > > > Yes, that's a very good proposal Jark.
> > > > >> > > > +1
> > > > >> > > >
> > > > >> > > > Best, Fabian
> > > > >> > > >
> > > > >> > > > Am Mo., 6. Mai 2019 um 16:33 Uhr schrieb Till Rohrmann <
> > > > >> > > > trohrm...@apache.org
> > > > >> > > > >:
> > > > >> > > >
> > > > >> > > > > I think this is a good idea Jark. Putting the last update
> > date
> > > > on
> > > > >> the
> > > > >> > > > > roadmap would also force us to regularly update it.
> > > > >> > > > >
> > > > >> > > > > Cheers,
> > > > >> > > > > Till
> > > > >> > > > >
> &

Re: [DISCUSS] Update our Roadmap

[Marta Paes Moreira]

Thanks for bringing this up, Robert.

More than updating the roadmap, it would be valuable to discuss how to make
this update systematic. I took care of the last update back in September
and - to be honest - the effort for someone who is not involved in release
planning (or at least for me) feels unnecessarily high.

One way to ensure that the roadmap is kept fresh could be to make the
update part of the release kick-off (for example, as part of the
responsibilities of the release managers).

What do you think?

Marta

On Mon, May 4, 2020 at 10:35 PM Robert Metzger  wrote:

> Hey all,
> The roadmap has been updated last in September 2019. There is quite a bit
> of outdated information on that page.
>
> Is there a volunteer who wants to create a first draft for an updated
> version?
>
> On Mon, Aug 19, 2019 at 12:14 PM Robert Metzger 
> wrote:
>
> > Nice, thanks! Looking forward to the PR
> >
> > On Mon, Aug 19, 2019 at 11:08 AM Marta Paes Moreira  >
> > wrote:
> >
> >> Hey, Robert.
> >>
> >> Updating the roadmap is something I can work on (and also have on my
> >> radar,
> >> moving forward). Already had a quick word with Stephan and he's
> available
> >> to provide support, if needed.
> >>
> >> Marta
> >>
> >> On Sun, Aug 18, 2019 at 4:46 PM Stephan Ewen  wrote:
> >>
> >> > I could help with that.
> >> >
> >> > On Fri, Aug 16, 2019 at 2:36 PM Robert Metzger 
> >> > wrote:
> >> >
> >> > > Flink 1.9 is feature freezed and almost released.
> >> > > I guess it makes sense to update the roadmap on the website again.
> >> > >
> >> > > Who feels like having a good overview of what's coming up?
> >> > >
> >> > > On Tue, May 7, 2019 at 4:33 PM Fabian Hueske 
> >> wrote:
> >> > >
> >> > > > Yes, that's a very good proposal Jark.
> >> > > > +1
> >> > > >
> >> > > > Best, Fabian
> >> > > >
> >> > > > Am Mo., 6. Mai 2019 um 16:33 Uhr schrieb Till Rohrmann <
> >> > > > trohrm...@apache.org
> >> > > > >:
> >> > > >
> >> > > > > I think this is a good idea Jark. Putting the last update date
> on
> >> the
> >> > > > > roadmap would also force us to regularly update it.
> >> > > > >
> >> > > > > Cheers,
> >> > > > > Till
> >> > > > >
> >> > > > > On Mon, May 6, 2019 at 4:14 AM Jark Wu 
> wrote:
> >> > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > One suggestion for the roadmap:
> >> > > > > >
> >> > > > > > Shall we add a `latest-update-time` to the top of Roadmap
> page?
> >> So
> >> > > that
> >> > > > > > users can know this is a up-to-date Roadmap.
> >> > > > > >
> >> > > > > > On Thu, 2 May 2019 at 04:49, Bowen Li 
> >> wrote:
> >> > > > > >
> >> > > > > > > +1
> >> > > > > > >
> >> > > > > > > On Mon, Apr 29, 2019 at 11:41 PM jincheng sun <
> >> > > > > sunjincheng...@gmail.com>
> >> > > > > > > wrote:
> >> > > > > > >
> >> > > > > > > > Hi Jeff&Fabian,
> >> > > > > > > >
> >> > > > > > > > I have open the PR about add Python Table API section to
> the
> >> > > > > roadmap. I
> >> > > > > > > > appreciate if you have time to look at it. :)
> >> > > > > > > >
> >> > > > > > > > https://github.com/apache/flink-web/pull/204
> >> > > > > > > >
> >> > > > > > > > Regards,
> >> > > > > > > > Jincheng
> >> > > > > > > >
> >> > > > > > > > jincheng sun  于2019年4月29日周一
> >> > 下午11:12写道：
> >> > > > > > > >
> >> > > > > > > > > Sure, I will do it！I think the python table api info
> >> should
> >> > in
> >> > > > the
> 

Re: [DISCUSS] Send issue and pull request notifications for flink-web and flink-shaded to iss...@flink.apache.org

[Marta Paes Moreira]

+1, this is quite annoying and distracting.

Marta

On Mon, May 4, 2020 at 6:27 PM Yu Li  wrote:

> +1
>
> Best Regards,
> Yu
>
>
> On Tue, 5 May 2020 at 00:21, Konstantin Knauf  wrote:
>
> > Yes, please.
> >
> > On Mon, May 4, 2020 at 5:50 PM Dawid Wysakowicz 
> > wrote:
> >
> > > +1
> > >
> > > Yes, please. I've also observed a lot of noise in the past days.
> > >
> > > Best,
> > >
> > > Dawid
> > >
> > > On 04/05/2020 17:48, Tzu-Li (Gordon) Tai wrote:
> > > > +1
> > > >
> > > > All the recent new repos, flink-statefun / flink-statefun-docker /
> > > > flink-training etc. are also sending notifications to issues@.
> > > >
> > > > Gordon
> > > >
> > > >
> > > > On Mon, May 4, 2020, 11:44 PM Till Rohrmann 
> > > wrote:
> > > >
> > > >> Hi everyone,
> > > >>
> > > >> due to some changes on the ASF side, we are now seeing issue and
> pull
> > > >> request notifications for the flink-web [1] and flink-shaded [2]
> repo
> > on
> > > >> dev@flink.apache.org. I think this is not ideal since the dev ML is
> > > much
> > > >> more noisy now.
> > > >>
> > > >> I would propose to send these notifications to
> > iss...@flink.apache.org
> > > as
> > > >> we are currently doing it for the Flink main repo [3].
> > > >>
> > > >> What do you think?
> > > >>
> > > >> [1] https://github.com/apache/flink-web
> > > >> [2] https://github.com/apache/flink-shaded
> > > >> [3] https://gitbox.apache.org/schemes.cgi?flink
> > > >>
> > > >> Cheers,
> > > >> Till
> > > >>
> > >
> > >
> >
> > --
> >
> > Konstantin Knauf
> >
> > https://twitter.com/snntrable
> >
> > https://github.com/knaufk
> >
>

Re: [PROPOSAL] Google Season of Docs 2020.

[Marta Paes Moreira]

The application to Season of Docs 2020 is close to being finalized. I've
created a PR with the application announcement for the Flink blog [1] (as
required by Google OSS).

Thanks a lot to everyone who pitched in — and special thanks to Aljoscha
and Seth for volunteering as mentors!

I'll send an update to this thread once the results are out (May 11th).

[1] https://github.com/apache/flink-web/pull/332

On Mon, Apr 27, 2020 at 9:28 PM Seth Wiesman  wrote:

> Hi Marta,
>
> I think this is a great idea, I'd be happy to help mentor a table
> documentation project.
>
> Seth
>
> On Thu, Apr 23, 2020 at 8:38 AM Marta Paes Moreira 
> wrote:
>
> > Thanks for the feedback!
> >
> > So far, the projects on the table are:
> >
> >1. Improving the Table API/SQL documentation.
> >2. Improving the documentation about Deployments.
> >3. Restructuring and standardizing the documentation about Connectors.
> >4. Finishing the Chinese translation.
> >
> > I think 2. would require a lot of technical knowledge about Flink, which
> > might not be a good fit for GSoD (as discussed last year).
> >
> > As for mentors, we have:
> >
> >- Aljoscha (Table API/SQL)
> >- Till (Deployments)
> >- Stephan also said he'd be happy to participate as a mentor if
> needed.
> >
> > For the translation project, I'm pulling in the people involved in last
> > year's thread (Jark and Jincheng), as we would need two chinese-speaking
> > mentors.
> >
> > I'll follow up with a draft proposal early next week, once we reach a
> > consensus and have enough mentors (2 per project). Thanks again!
> >
> > Marta
> >
> >
> > On Fri, Apr 17, 2020 at 2:53 PM Till Rohrmann 
> > wrote:
> >
> > > Thanks for driving this effort Marta.
> > >
> > > I'd be up for mentoring improvements for the deployment section as
> > > described in FLIP-42.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Fri, Apr 17, 2020 at 11:20 AM Aljoscha Krettek  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > first, excellent that you're driving this, Marta!
> > > >
> > > > By now I have made quite some progress on the FLIP-42 restructuring
> so
> > > > that is not a good effort for someone to join now. Plus there is also
> > > > [1], which is about incorporating the existing Flink Training
> material
> > > > into the concepts section of the Flink doc.
> > > >
> > > > What I think would be very good is working on the Table API/SQL
> > > > documentation [2]. We don't necessarily have to take the FLIP as a
> > basis
> > > > but we can, or we can start from a blank slate. I think the current
> > > > structure as well as the content is sub-optimal (not good, really).
> It
> > > > would be ideal to have someone get to now the system and then write
> > > > documentation for that part of Flink that has both good structure and
> > > > content and nicely guides new users.
> > > >
> > > > I would be very happy to mentor that effort.
> > > >
> > > > Best,
> > > > Aljoscha
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/rea9cbfffd9a1c0ca6f78f7e8c8497d81f32ed4a7b9e7a05d59f3b2e9%40%3Cdev.flink.apache.org%3E
> > > >
> > > > [2]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405685
> > > >
> > > > On 17.04.20 09:21, Robert Metzger wrote:
> > > > > Thanks a lot for volunteering to drive an application for the Flink
> > > > project!
> > > > >
> > > > > Last year, we discussed finishing the chinese translation as a
> > > potential
> > > > > project. I believe there's still a need for this.
> > > > > Since the work on the project starts pretty far in the future
> > > > (September),
> > > > > the translation project is a good fit as well (there's currently no
> > > major
> > > > > effort on the translation, rather a constant flow of PRs, but I
> don't
> > > > think
> > > > > that is enough to finish the translation).
> > > > >
> > > > >
> > > > > On Fri, Apr 17, 2020 at 9:15 AM Konstantin Knauf &

Re: [PROPOSAL] Google Season of Docs 2020.

[Marta Paes Moreira]

Hi, Manish.

If you would like to contribute to Flink, please read the "How to
Contribute" section on the website [1]. This thread has a different scope.

Feel free to reach out (in a separate thread) if you have any questions.

Marta

[1] https://flink.apache.org/contributing/how-to-contribute.html

On Thu, Apr 23, 2020 at 3:44 PM Manish G 
wrote:

> Hi,
>
> I would also like to contribute to documentation and unit testing.
> Please let me know.
>
> Manish
>
> On Thu, Apr 23, 2020 at 7:08 PM Marta Paes Moreira 
> wrote:
> >
> > Thanks for the feedback!
> >
> > So far, the projects on the table are:
> >
> >1. Improving the Table API/SQL documentation.
> >2. Improving the documentation about Deployments.
> >3. Restructuring and standardizing the documentation about Connectors.
> >4. Finishing the Chinese translation.
> >
> > I think 2. would require a lot of technical knowledge about Flink, which
> > might not be a good fit for GSoD (as discussed last year).
> >
> > As for mentors, we have:
> >
> >- Aljoscha (Table API/SQL)
> >- Till (Deployments)
> >- Stephan also said he'd be happy to participate as a mentor if
> needed.
> >
> > For the translation project, I'm pulling in the people involved in last
> > year's thread (Jark and Jincheng), as we would need two chinese-speaking
> > mentors.
> >
> > I'll follow up with a draft proposal early next week, once we reach a
> > consensus and have enough mentors (2 per project). Thanks again!
> >
> > Marta
> >
> >
> > On Fri, Apr 17, 2020 at 2:53 PM Till Rohrmann 
> wrote:
> >
> > > Thanks for driving this effort Marta.
> > >
> > > I'd be up for mentoring improvements for the deployment section as
> > > described in FLIP-42.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Fri, Apr 17, 2020 at 11:20 AM Aljoscha Krettek  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > first, excellent that you're driving this, Marta!
> > > >
> > > > By now I have made quite some progress on the FLIP-42 restructuring
> so
> > > > that is not a good effort for someone to join now. Plus there is also
> > > > [1], which is about incorporating the existing Flink Training
> material
> > > > into the concepts section of the Flink doc.
> > > >
> > > > What I think would be very good is working on the Table API/SQL
> > > > documentation [2]. We don't necessarily have to take the FLIP as a
> basis
> > > > but we can, or we can start from a blank slate. I think the current
> > > > structure as well as the content is sub-optimal (not good, really).
> It
> > > > would be ideal to have someone get to now the system and then write
> > > > documentation for that part of Flink that has both good structure and
> > > > content and nicely guides new users.
> > > >
> > > > I would be very happy to mentor that effort.
> > > >
> > > > Best,
> > > > Aljoscha
> > > >
> > > > [1]
> > > >
> > > >
> > >
> https://lists.apache.org/thread.html/rea9cbfffd9a1c0ca6f78f7e8c8497d81f32ed4a7b9e7a05d59f3b2e9%40%3Cdev.flink.apache.org%3E
> > > >
> > > > [2]
> > > >
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405685
> > > >
> > > > On 17.04.20 09:21, Robert Metzger wrote:
> > > > > Thanks a lot for volunteering to drive an application for the Flink
> > > > project!
> > > > >
> > > > > Last year, we discussed finishing the chinese translation as a
> > > potential
> > > > > project. I believe there's still a need for this.
> > > > > Since the work on the project starts pretty far in the future
> > > > (September),
> > > > > the translation project is a good fit as well (there's currently no
> > > major
> > > > > effort on the translation, rather a constant flow of PRs, but I
> don't
> > > > think
> > > > > that is enough to finish the translation).
> > > > >
> > > > >
> > > > > On Fri, Apr 17, 2020 at 9:15 AM Konstantin Knauf <
> kna...@apache.org>
> > > > wrote:
> > > > >
> > > > >> Hi Marta,
> > > > >>
> &

Re: [PROPOSAL] Google Season of Docs 2020.

[Marta Paes Moreira]

Thanks for the feedback!

So far, the projects on the table are:

   1. Improving the Table API/SQL documentation.
   2. Improving the documentation about Deployments.
   3. Restructuring and standardizing the documentation about Connectors.
   4. Finishing the Chinese translation.

I think 2. would require a lot of technical knowledge about Flink, which
might not be a good fit for GSoD (as discussed last year).

As for mentors, we have:

   - Aljoscha (Table API/SQL)
   - Till (Deployments)
   - Stephan also said he'd be happy to participate as a mentor if needed.

For the translation project, I'm pulling in the people involved in last
year's thread (Jark and Jincheng), as we would need two chinese-speaking
mentors.

I'll follow up with a draft proposal early next week, once we reach a
consensus and have enough mentors (2 per project). Thanks again!

Marta


On Fri, Apr 17, 2020 at 2:53 PM Till Rohrmann  wrote:

> Thanks for driving this effort Marta.
>
> I'd be up for mentoring improvements for the deployment section as
> described in FLIP-42.
>
> Cheers,
> Till
>
> On Fri, Apr 17, 2020 at 11:20 AM Aljoscha Krettek 
> wrote:
>
> > Hi,
> >
> > first, excellent that you're driving this, Marta!
> >
> > By now I have made quite some progress on the FLIP-42 restructuring so
> > that is not a good effort for someone to join now. Plus there is also
> > [1], which is about incorporating the existing Flink Training material
> > into the concepts section of the Flink doc.
> >
> > What I think would be very good is working on the Table API/SQL
> > documentation [2]. We don't necessarily have to take the FLIP as a basis
> > but we can, or we can start from a blank slate. I think the current
> > structure as well as the content is sub-optimal (not good, really). It
> > would be ideal to have someone get to now the system and then write
> > documentation for that part of Flink that has both good structure and
> > content and nicely guides new users.
> >
> > I would be very happy to mentor that effort.
> >
> > Best,
> > Aljoscha
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/rea9cbfffd9a1c0ca6f78f7e8c8497d81f32ed4a7b9e7a05d59f3b2e9%40%3Cdev.flink.apache.org%3E
> >
> > [2]
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405685
> >
> > On 17.04.20 09:21, Robert Metzger wrote:
> > > Thanks a lot for volunteering to drive an application for the Flink
> > project!
> > >
> > > Last year, we discussed finishing the chinese translation as a
> potential
> > > project. I believe there's still a need for this.
> > > Since the work on the project starts pretty far in the future
> > (September),
> > > the translation project is a good fit as well (there's currently no
> major
> > > effort on the translation, rather a constant flow of PRs, but I don't
> > think
> > > that is enough to finish the translation).
> > >
> > >
> > > On Fri, Apr 17, 2020 at 9:15 AM Konstantin Knauf 
> > wrote:
> > >
> > >> Hi Marta,
> > >>
> > >> Thanks for kicking off the discussion. Aljoscha has recently revived
> the
> > >> implementation of the FLIP-42 and has already moved things around
> quite
> > a
> > >> bit. [1]
> > >>
> > >> There are a lot of areas that can be improved of course, but a lot of
> > them
> > >> require very deep knowledge about the system (e.g. the "Deployment" or
> > >> "Concepts" section). One area that I could imagine working well in
> such
> > a
> > >> format is to work on the "Connectors" section. Aljoscha has already
> > moved
> > >> this to the top-level, but it besides that it has not been touched yet
> > in
> > >> the course of FLIP-42. The documentation project could be around
> > >> restructuring, standardization and generally improving the
> > documentation of
> > >> our connectors for both Datastream as well as Table API/SQL.
> > >>
> > >> Cheers,
> > >>
> > >> Konstantin
> > >>
> > >> [1] https://ci.apache.org/projects/flink/flink-docs-master/
> > >>
> > >> On Wed, Apr 15, 2020 at 12:11 PM Marta Paes Moreira <
> > ma...@ververica.com>
> > >> wrote:
> > >>
> > >>> Hi, Everyone.
> > >>>
> > >>> Google is running its Season of Docs [1] pr

[PROPOSAL] Google Season of Docs 2020.

[Marta Paes Moreira]

Hi, Everyone.

Google is running its Season of Docs [1] program again this year. The goal
of the program is to pair open source organizations/projects with
professional technical writers to improve their documentation.

The Flink community submitted an application in 2019 (led by Konstantin)
[2,3], but was unfortunately not accepted into the program. This year, I'm
volunteering to write and submit the proposal in the upcoming weeks. To
achieve this, there are a few things that need to be sorted out in advance:

   -
*Mentors *Each proposed project idea requires at least two volunteers to
   mentor technical writers through the process. *Who would like to
   participate as a mentor*? You can read about the responsibilities here
   [4].


   -
*Project Ideas *We can submit as many project ideas as we'd like, but it's
   unlikely that more than 2 are accepted. *What would you consider a
   priority for documentation improvement*? In my opinion, reorganizing the
   documentation to make it easier to navigate and more accessible to
   newcomers would be a top priority. You can check FLIP-42/FLINK-12639 [5]
   for improvements that are already under consideration and [6] for last
   year's mailing list discussion.


   - *Alternative Organization Administrator*
   I volunteer as an administrator, but Google requires two. *Who would
   like to join me as an application administrator*?

The deadline is *May 4th *and the accepted projects would kick-off the work
with technical writers on *September 14th*. Let me know if you have any
questions!

Thanks,

Marta

[1] https://developers.google.com/season-of-docs
[2]
https://lists.apache.org/thread.html/3c789b6187da23ad158df59bbc598543b652e3cfc1010a14e294e16a@%3Cdev.flink.apache.org%3E
[3]
https://docs.google.com/document/d/1Up53jNsLztApn-mP76AB6xWUVGt3nwS9p6xQTiceKXo/edit?usp=sharing
[4] https://developers.google.com/season-of-docs/docs/mentor-guide
[5] https://issues.apache.org/jira/browse/FLINK-12639
[6]
https://lists.apache.org/thread.html/3c789b6187da23ad158df59bbc598543b652e3cfc1010a14e294e16a@%3Cdev.flink.apache.org%3E

Re: [ANNOUNCE] Apache Flink Stateful Functions 2.0.0 released

[Marta Paes Moreira]

Thank you for managing the release, Gordon — you did a tremendous job! And
to everyone else who worked on pushing it through.

Really excited about the new use cases that StateFun 2.0 unlocks for Flink
users and beyond!

Marta

On Tue, Apr 7, 2020 at 4:47 PM Hequn Cheng  wrote:

> Thanks a lot for the release and your great job, Gordon!
> Also thanks to everyone who made this release possible!
>
> Best,
> Hequn
>
> On Tue, Apr 7, 2020 at 8:58 PM Tzu-Li (Gordon) Tai 
> wrote:
>
>> The Apache Flink community is very happy to announce the release of
>> Apache Flink Stateful Functions 2.0.0.
>>
>> Stateful Functions is an API that simplifies building distributed
>> stateful applications.
>> It's based on functions with persistent state that can interact
>> dynamically with strong consistency guarantees.
>>
>> Please check out the release blog post for an overview of the release:
>> https://flink.apache.org/news/2020/04/07/release-statefun-2.0.0.html
>>
>> The release is available for download at:
>> https://flink.apache.org/downloads.html
>>
>> Maven artifacts for Stateful Functions can be found at:
>> https://search.maven.org/search?q=g:org.apache.flink%20statefun
>>
>> Python SDK for Stateful Functions published to the PyPI index can be
>> found at:
>> https://pypi.org/project/apache-flink-statefun/
>>
>> Official Docker image for building Stateful Functions applications is
>> currently being published to Docker Hub.
>> Dockerfiles for this release can be found at:
>> https://github.com/apache/flink-statefun-docker/tree/master/2.0.0
>> Progress for creating the Docker Hub repository can be tracked at:
>> https://github.com/docker-library/official-images/pull/7749
>>
>> The full release notes are available in Jira:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12346878
>>
>> We would like to thank all contributors of the Apache Flink community who
>> made this release possible!
>>
>> Cheers,
>> Gordon
>>
>

[jira] [Created] (FLINK-16978) Update flink-statefun README.md for Stateful Functions 2.0.

[Marta Paes Moreira (Jira)]

Marta Paes Moreira created FLINK-16978:
--

 Summary: Update flink-statefun README.md for Stateful Functions 
2.0.
 Key: FLINK-16978
 URL: https://issues.apache.org/jira/browse/FLINK-16978
 Project: Flink
  Issue Type: Task
  Components: Stateful Functions
Reporter: Marta Paes Moreira
Assignee: Marta Paes Moreira


Updating the README in the repository to fit the changes of Stateful Functions 
2.0.

Will also update the README in the statefun-python-sdk directory.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (FLINK-16677) Make Stateful Functions more prominent in the Flink website.

[Marta Paes Moreira (Jira)]

Marta Paes Moreira created FLINK-16677:
--

 Summary: Make Stateful Functions more prominent in the Flink 
website.
 Key: FLINK-16677
 URL: https://issues.apache.org/jira/browse/FLINK-16677
 Project: Flink
  Issue Type: Task
  Components: Project Website, Stateful Functions
Reporter: Marta Paes Moreira
Assignee: Marta Paes Moreira


As discussed in the @dev Mailing List [1], we'd like to give Stateful Functions 
more visibility in the Flink website. The consensus is that a bigger update of 
the landing page is needed, but in the meantime, the following modifications 
will be made to the navigation sidebar:
 * (+) What is "Stateful Functions"? link
 * (+) StateFun on GitHub link


[1] 
[https://lists.apache.org/thread.html/r819fc97e83c5e4cb5abc5e4a6f49862012bfe9a3742b3f25ac2d9117%40%3Cdev.flink.apache.org%3E]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (FLINK-16449) Deprecated methods in the Table API walkthrough.

[Marta Paes Moreira (Jira)]

Marta Paes Moreira created FLINK-16449:
--

 Summary: Deprecated methods in the Table API walkthrough.
 Key: FLINK-16449
 URL: https://issues.apache.org/jira/browse/FLINK-16449
 Project: Flink
  Issue Type: Improvement
  Components: Quickstarts, Table SQL / API
Affects Versions: 1.10.0
Reporter: Marta Paes Moreira


The sample code provided for the Table API walkthrough [1] includes methods 
that have been deprecated in Flink 1.10 (FLIP-64): registerTableSource, 
registerTableSink, scan.

This can be confusing to users trying to get started, also because finding how 
to use the alternative methods is not very intuitive.

[1] 
[https://ci.apache.org/projects/flink/flink-docs-release-1.10/getting-started/walkthroughs/table_api.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Update our Roadmap

[Marta Paes Moreira]

Hey, Robert.

Updating the roadmap is something I can work on (and also have on my radar,
moving forward). Already had a quick word with Stephan and he's available
to provide support, if needed.

Marta

On Sun, Aug 18, 2019 at 4:46 PM Stephan Ewen  wrote:

> I could help with that.
>
> On Fri, Aug 16, 2019 at 2:36 PM Robert Metzger 
> wrote:
>
> > Flink 1.9 is feature freezed and almost released.
> > I guess it makes sense to update the roadmap on the website again.
> >
> > Who feels like having a good overview of what's coming up?
> >
> > On Tue, May 7, 2019 at 4:33 PM Fabian Hueske  wrote:
> >
> > > Yes, that's a very good proposal Jark.
> > > +1
> > >
> > > Best, Fabian
> > >
> > > Am Mo., 6. Mai 2019 um 16:33 Uhr schrieb Till Rohrmann <
> > > trohrm...@apache.org
> > > >:
> > >
> > > > I think this is a good idea Jark. Putting the last update date on the
> > > > roadmap would also force us to regularly update it.
> > > >
> > > > Cheers,
> > > > Till
> > > >
> > > > On Mon, May 6, 2019 at 4:14 AM Jark Wu  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > One suggestion for the roadmap:
> > > > >
> > > > > Shall we add a `latest-update-time` to the top of Roadmap page? So
> > that
> > > > > users can know this is a up-to-date Roadmap.
> > > > >
> > > > > On Thu, 2 May 2019 at 04:49, Bowen Li  wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Mon, Apr 29, 2019 at 11:41 PM jincheng sun <
> > > > sunjincheng...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Jeff&Fabian,
> > > > > > >
> > > > > > > I have open the PR about add Python Table API section to the
> > > > roadmap. I
> > > > > > > appreciate if you have time to look at it. :)
> > > > > > >
> > > > > > > https://github.com/apache/flink-web/pull/204
> > > > > > >
> > > > > > > Regards,
> > > > > > > Jincheng
> > > > > > >
> > > > > > > jincheng sun  于2019年4月29日周一
> 下午11:12写道：
> > > > > > >
> > > > > > > > Sure, I will do it！I think the python table api info should
> in
> > > the
> > > > > > > >  roadmap! Thank you @Jeff @Fabian
> > > > > > > >
> > > > > > > > Fabian Hueske 于2019年4月29日 周一23:05写道：
> > > > > > > >
> > > > > > > >> Great, thanks Jeff and Timo!
> > > > > > > >>
> > > > > > > >> @Jincheng do you want to write a paragraph about the Python
> > > effort
> > > > > and
> > > > > > > >> open a PR for it?
> > > > > > > >>
> > > > > > > >> I'll remove the issue about Hadoop convenience builds
> > > > (FLINK-11266).
> > > > > > > >>
> > > > > > > >> Best, Fabian
> > > > > > > >>
> > > > > > > >> Am Mo., 29. Apr. 2019 um 16:37 Uhr schrieb Jeff Zhang <
> > > > > > zjf...@gmail.com
> > > > > > > >:
> > > > > > > >>
> > > > > > > >>> jincheng(cc) is driving the python effort, I think he can
> > help
> > > to
> > > > > > > >>> prepare it.
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>> Fabian Hueske  于2019年4月29日周一 下午10:15写道：
> > > > > > > >>>
> > > > > > >  Hi everyone,
> > > > > > > 
> > > > > > >  Since we had no more comments on this thread, I think we
> > > proceed
> > > > > to
> > > > > > >  update the roadmap.
> > > > > > > 
> > > > > > >  @Jeff Zhang  I agree, we should add the
> > > > Python
> > > > > > >  efforts to the roadmap.
> > > > > > >  Do you want to prepare a short paragraph that we can add
> to
> > > the
> > > > > > >  document?
> > > > > > > 
> > > > > > >  Best, Fabian
> > > > > > > 
> > > > > > >  Am Mi., 17. Apr. 2019 um 15:04 Uhr schrieb Jeff Zhang <
> > > > > > > zjf...@gmail.com
> > > > > > >  >:
> > > > > > > 
> > > > > > > > Hi Fabian,
> > > > > > > >
> > > > > > > > One thing missing is python api and python udf, we
> already
> > > > > > discussed
> > > > > > > > it in
> > > > > > > > community, and it is very close to reach consensus.
> > > > > > > >
> > > > > > > >
> > > > > > > > Fabian Hueske  于2019年4月17日周三
> 下午7:51写道：
> > > > > > > >
> > > > > > > > > Hi everyone,
> > > > > > > > >
> > > > > > > > > We recently added a roadmap to our project website [1]
> > and
> > > > > > decided
> > > > > > > to
> > > > > > > > > update it after every release. Flink 1.8.0 was
> released a
> > > few
> > > > > > days
> > > > > > > > ago, so
> > > > > > > > > I think it we should check and remove from the roadmap
> > what
> > > > was
> > > > > > > > achieved so
> > > > > > > > > far and add features / improvements that we plan for
> the
> > > > > future.
> > > > > > > > >
> > > > > > > > > I had a look at the roadmap and found that
> > > > > > > > >
> > > > > > > > > > We are changing the build setup to not bundle Hadoop
> by
> > > > > > default,
> > > > > > > > but
> > > > > > > > > rather offer pre-packaged
> > > > > > > > > > Hadoop libraries for the use with Yarn, HDFS, etc. as
> > > > > > convenience
> > > > > > > > > downloads FLINK-11266 <
> > > > > > > > https://issues.apache.org/jira/browse/FLINK-11266>.
> > > > > > > > 

Re: [DISCUSS] Create a Flink ecosystem website

[Marta Paes Moreira]

Hey, Robert.

I will keep an eye on the overall progress and get started on the blog post
to make the community announcement. Are there (mid-term) plans to
translate/localize this website as well? It might be a point worth
mentioning in the blogpost.

Hats off to you and Daryl — this turned out amazing!

Marta

On Thu, Jul 18, 2019 at 10:57 AM Congxian Qiu 
wrote:

> Robert and Daryl, thanks for the great work, I tried the website and filed
> some issues on Github.
> Best,
> Congxian
>
>
> Robert Metzger  于2019年7月17日周三 下午11:28写道：
>
>> Hey all,
>>
>> Daryl and I have great news to share. We are about to finish adding the
>> basic features to the ecosystem page.
>> We are at a stage where it is ready to be reviewed and made public.
>>
>> You can either check out a development instance of the ecosystem page
>> here: https://flink-ecosystem-demo.flink-resources.org/
>> Or you run it locally, with the instructions from the README.md:
>> https://github.com/sorahn/flink-ecosystem
>>
>> Please report all issues you find here:
>> https://github.com/sorahn/flink-ecosystem/issues or in this thread.
>>
>> The next steps in this project are the following:
>> - We fix all issues reported through this testing
>> - We set up the site on the INFRA resources Becket has secured [1], do
>> some further testing (including email notifications) and pre-fill the page
>> with some packages.
>> - We set up a packages.flink.apache.org or flink.apache.org/packages
>> domain
>> - We announce the packages through a short blog post
>>
>> Happy testing!
>>
>> Best,
>> Robert
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-18010
>>
>>
>> On Thu, Apr 25, 2019 at 6:23 AM Becket Qin  wrote:
>>
>>> Thanks for the update, Robert. Looking forward to the website. If there
>>> is already a list of software we need to run the website, we can ask Apache
>>> infra team to prepare the VM for us, as that may also take some time.
>>>
>>> On Wed, Apr 24, 2019 at 11:57 PM Robert Metzger 
>>> wrote:
>>>
 Hey all,

 quick update on this project: The frontend and backend code have been
 put together into this repository:
 https://github.com/sorahn/flink-ecosystem
 We also just agreed on an API specification, and will now work on
 finishing the backend.

 It will probably take a few more weeks for this to finish, but we are
 making progress :)

 Best,
 Robert


 On Mon, Apr 15, 2019 at 11:18 AM Robert Metzger 
 wrote:

> Hey Daryl,
>
> thanks a lot for posting a link to this first prototype on the mailing
> list! I really like it!
>
> Becket: Our plan forward is that Congxian is implementing the backend
> for the website. He has already started with the work, but needs at least
> one more week.
>
>
> [Re-sending this email because the first one was blocked on dev@f.a.o]
>
>
> On Mon, Apr 15, 2019 at 7:59 AM Becket Qin 
> wrote:
>
>> Hi Daryl,
>>
>> Thanks a lot for the update. The site looks awesome! This is a great
>> progress. I really like the conciseness of GUI.
>>
>> One minor suggestion is that for the same library, there might be
>> multiple versions compatible with different Flink versions. It would be
>> good to show that somewhere in the project page as it seems important to
>> the users.
>>
>> BTW, will you share the plan to move forward? Would additional hands
>> help?
>>
>> Thanks,
>>
>> Jiangjie (Becket) Qin
>>
>> On Sat, Apr 13, 2019 at 7:10 PM Daryl Roberts 
>> wrote:
>>
>>> > Shall we add a guide page to show people how to publish their
>>> projects to the website? The exact rules can be discussed and drafted 
>>> in a
>>> separate email thread IMO
>>>
>>> This is a good idea. (Both the guise, and separate thread), I think
>>> once there is an actual packed in place we’ll be in a lot better 
>>> position
>>> to discuss this.
>>>
>>> > The "Log in with Github" link doesn't seem to work yet. Will it
>>> only allow login for admins and publishers, or for everyone?
>>>
>>> Correct, all the oauth stuff requires a real server. We are
>>> currently just faking everything.
>>>
>>> I will add a mock-login page (username/password that just accepts
>>> anything and displays whatever username you type in) so we can see the
>>> add-comment field and add-packages page once they exist.
>>>
>>>
>>>
>>>

Re: [ANNOUNCE] Weekly Community Update 2019/25

[Marta Paes Moreira]

Hi, Robert.

Using these digests for that purpose is something I also discussed with
Konstantin, so I believe we are aligned on this. A monthly community update
could go a bit beyond and recap on events (e.g. meetups, conferences) and
other relevant work that is brewing in the community.

If everyone is on board with the idea, I can take the initiative to write
these up on the Flink blog.

Thanks!

On Fri, Jun 28, 2019 at 9:51 AM Robert Metzger  wrote:

> Thank you for the update! I always enjoy reading them.
>
> Maybe we could use these threads as an input for a monthly "Community
> Update" blog post series?
> I've discussed this idea offline already my colleague Marta. Are you still
> interested?
>
>
>
> On Sun, Jun 23, 2019 at 10:18 PM Konstantin Knauf <
> konstan...@ververica.com>
> wrote:
>
> > Dear community,
> >
> > this week's update contains a few pointers to upcoming changes in the
> > development process, two recent proposals around metrics as well as
> smaller
> > discussions on the dev mailing list. Still processing the backlog of
> topics
> > & discussions by including a few of them each week.
> >
> > As always, please feel free to add additional updates and news to this
> > thread!
> >
> > Flink Development
> > ===
> >
> > * [development-process] Back in February the Flink community discussed
> > changes to its *code contribution process* (implemented in Jira) [1]. In
> > the future only committers will be able to assign contributors to tickets
> > hopefully moving discussions to an earlier stage in the contribution
> > process. The new process has now been fully documented and published on
> the
> > Flink Website [2]. As far as I know, the next step is changing the Jira
> > permissions accordingly.
> >
> > * [development-process] Stephan has recently started a conversation about
> > adopting a c*ode style and quality guide* for contributions to Apache
> > Flink. It covers Flink-specific aspects like PR naming, but also general
> > Java best practices and lessons-learned in the context of a complex
> system
> > like Flink. The feedback was quite positive and Robert is now going to
> > split the guide into subsections and add it to the Flink website. [3]
> >
> > * [releases] The last currently known blocker for* Flink 1.8.1* has been
> > resolved and Jincheng is in the process of creating a first release
> > candidate. [4]
> >
> > * [releases] The feature freeze for *Flink 1.9.0 *has been set to the
> > originally proposed date, 28th of June [5,6].
> >
> > * [metrics] In May Hwanju proposed to significantly enhance the
> *availability
> > metrics* of Flink and classify downtimes based on the root cause of the
> > failure (mainly between system and user code). [8] This will make it
> easier
> > for service providers to monitor the SLAs of a Flink-based service. The
> > discussion thread has by now been split into two design documents for
> > exception classification [9] and more fine-grained execution tracking
> [10].
> >
> > * [metrics] Becket proposed to standardize the metrics provided by
> > connectors. It defines a set of *standard metrics*, which each source or
> > sink should expose (e.g. numBytesIn, pendingRecord). As far as I can
> > tell, the FLIP is still being voted on with positive feedback so far
> [11].
> >
> > * Dyana brought up the possibility to include the *Kinesis Connector*
> > module in the official Apache Flink releases as these are now available
> > under Apache 2.0 license. The corresponding contribution is pending. [12]
> >
> > * Xingcam started a discussion of whether to deprecate, fix or replace
> the
> > split/select methods of the DataStream API. They were marked deprecated
> in
> > Flink 1.8.0, but the current discussion has not come to a conclusion yet
> on
> > whether to really remove them going forward.
> >
> > [1]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-A-more-restrictive-JIRA-workflow-td27344.html
> > [2] https://flink.apache.org/contributing/contribute-code.html
> > [3]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Adopting-a-Code-Style-and-Quality-Guide-td29524.html#a29532
> > [4]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Releasing-Flink-1-8-1-td29154.html
> > [5]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html
> > [6]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Feature-freeze-for-Apache-Flink-1-9-0-release-td29751.html
> > [7]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Proposal-for-Flink-job-execution-availability-metrics-impovement-td28882.html
> > [8]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-33-Standardize-connector-metrics-td26869.html
> > [9]
> >
> https://docs.google.com/document/d/1pcHg9F3GoDDeVD5GIIo2wO67Hmjgy0-hRDeuFnrMgT4/edit#heading=h.v3ssap5tvszp
> >