Re: Flink Forward Europe 2019 - Call for Presentations open until 17th May

2019-05-20 Thread Oytun Tez
Thanks for the update, Robert!

I am planning to prepare a use case content with how we use Flink at
MotaWord, focusing more on Flink as "application framework", rather than
confining our mindset to Flink as "stream processor", on non-Uber,
non-Alibaba scales. Hopefully over the weekend, I should be ready to submit
CFP.




---
Oytun Tez

*M O T A W O R D*
The World's Fastest Human Translation Platform.
oy...@motaword.com — www.motaword.com


On Fri, May 17, 2019 at 11:02 AM Robert Metzger  wrote:

> Hey all,
>
> Short update on the Flink Forward Call For Presentations: We've extended
> the submission deadline till May 31 ... so there's more time to finish the
> talk abstracts.
>
> Also, the organizers are now able to cover travel costs for speakers in
> cases where an employer can not cover them.
>
>
>
> On Fri, May 10, 2019 at 9:38 AM Fabian Hueske  wrote:
>
>> Hi Tim,
>>
>> Thanks for submitting a talk!
>> This sounds like a good and interesting use case to me.
>> Machine learning on streaming data is definitely a relevant and
>> interesting
>> topic for Flink Forward!
>>
>> Best,
>> Fabian
>>
>>
>> Am Mo., 6. Mai 2019 um 19:52 Uhr schrieb Tim Frey :
>>
>> > Hi All,
>> >
>> > Sounds interesting. I submitted a talk about using Flink for machine
>> > learning.
>> > However, I would also be happy to gain some community feedback if the
>> > topic is to the right interest of the community.
>> >
>> > In short, we use flink to train machine learning models and to then use
>> > the same models for predict then. Our goal was to determine if it is
>> > possible to predict crypto currency exchange rates by utilizing social
>> data
>> > from Twitter.
>> > I would talk about our experiences and describe how we leveraged online
>> > learning in conjunction with social data to determine if we are able to
>> > predict future currency exchange rates. I’ll point out the general
>> > architecture and describe the most interesting findings.
>> >
>> > Best
>> > Tim
>> >
>> > -Ursprüngliche Nachricht-
>> > Von: Robert Metzger 
>> > Gesendet: Montag, 6. Mai 2019 09:44
>> > An: Fabian Hueske 
>> > Cc: user ; dev ;
>> > commun...@flink.apache.org
>> > Betreff: Re: Flink Forward Europe 2019 - Call for Presentations open
>> until
>> > 17th May
>> >
>> > Thanks for announcing the Call for Presentations here!
>> >
>> > Since the deadline is approaching, I wanted to bump up this thread to
>> > remind everybody to submit talks!
>> > Please reach out to me or Fabian directly if you have any questions or
>> if
>> > you need any support!
>> >
>> >
>> >
>> > On Thu, Apr 11, 2019 at 3:47 PM Fabian Hueske 
>> wrote:
>> >
>> > > Hi all,
>> > >
>> > > Flink Forward Europe returns to Berlin on October 7-9th, 2019.
>> > > We are happy to announce that the Call for Presentations is open!
>> > >
>> > > Please submit a proposal if you'd like to present your Apache Flink
>> > > experience, best practices, new features, or use cases in front of an
>> > > international audience of highly skilled and enthusiastic Flink users
>> > > and committers.
>> > >
>> > > Flink Forward will run tracks for the following topics:
>> > > * Use Case
>> > > * Operations
>> > > * Technology Deep Dive
>> > > * Ecosystem
>> > > * Research
>> > >
>> > > For the first time, we'll also have a Community track.
>> > >
>> > > Please find the submission form at
>> > > https://berlin-2019.flink-forward.org/call-for-presentations
>> > >
>> > > The deadline for submissions is May 17th, 11:59pm (CEST).
>> > >
>> > > Best regards,
>> > > Fabian
>> > > (PC Chair for Flink Forward Berlin 2019)
>> > >
>> >
>> >
>>
>


Re: [ANNOUNCE] Andrey Zagrebin becomes a Flink committer

2019-08-14 Thread Oytun Tez
Congratulations Andrey!

I am glad the Flink committer team is growing at such a pace!

---
Oytun Tez

*M O T A W O R D*
The World's Fastest Human Translation Platform.
oy...@motaword.com — www.motaword.com


On Wed, Aug 14, 2019 at 9:29 AM Zili Chen  wrote:

> Congratulations Andrey!
>
> Best,
> tison.
>
>
> Till Rohrmann  于2019年8月14日周三 下午9:26写道:
>
>> Hi everyone,
>>
>> I'm very happy to announce that Andrey Zagrebin accepted the offer of
>> the Flink PMC to become a committer of the Flink project.
>>
>> Andrey has been an active community member for more than 15 months. He
>> has helped shaping numerous features such as State TTL, FRocksDB release,
>> Shuffle service abstraction, FLIP-1, result partition management and
>> various fixes/improvements. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Andrey!
>>
>> Best, Till
>> (on behalf of the Flink PMC)
>>
>


Re: [ANNOUNCE] Apache Flink 1.9.0 released

2019-08-23 Thread Oytun Tez
Hi all,

We also had to rollback our upgrade effort for 2 reasons:

- Official Docker container is not ready yet
- This artefact is not published with
scala: org.apache.flink:flink-queryable-state-client-java_2.11:jar:1.9.0






---
Oytun Tez

*M O T A W O R D*
The World's Fastest Human Translation Platform.
oy...@motaword.com — www.motaword.com


On Fri, Aug 23, 2019 at 10:48 AM Zili Chen  wrote:

> Hi Till,
>
> Did we mention this in release note(or maybe previous release note where
> we did the exclusion)?
>
> Best,
> tison.
>
>
> Till Rohrmann  于2019年8月23日周五 下午10:28写道:
>
>> Hi Gavin,
>>
>> if I'm not mistaken, then the community excluded the Scala FlinkShell
>> since a couple of versions for Scala 2.12. The problem seems to be that
>> some of the tests failed. See here [1] for more information.
>>
>> [1] https://issues.apache.org/jira/browse/FLINK-10911
>>
>> Cheers,
>> Till
>>
>> On Fri, Aug 23, 2019 at 11:44 AM Gavin Lee  wrote:
>>
>>> I used package on apache official site, with mirror [1], the difference
>>> is
>>> I used scala 2.12 version.
>>> I also tried to build from source for both scala 2.11 and 2.12, when
>>> build
>>> 2.12 the FlinkShell.class is in flink-dist jar file but after running mvn
>>> clean package -Dscala-2.12, this class was removed in
>>> flink-dist_2.12-1.9 jar
>>> file.
>>> Seems broken here for scala 2.12, right?
>>>
>>> [1]
>>>
>>> http://mirror.bit.edu.cn/apache/flink/flink-1.9.0/flink-1.9.0-bin-scala_2.12.tgz
>>>
>>> On Fri, Aug 23, 2019 at 4:37 PM Zili Chen  wrote:
>>>
>>> > I downloaded 1.9.0 dist from here[1] and didn't see the issue. Where
>>> do you
>>> > download it? Could you try to download the dist from [1] and see
>>> whether
>>> > the problem last?
>>> >
>>> > Best,
>>> > tison.
>>> >
>>> > [1]
>>> >
>>> http://mirrors.tuna.tsinghua.edu.cn/apache/flink/flink-1.9.0/flink-1.9.0-bin-scala_2.11.tgz
>>> >
>>> >
>>> > Gavin Lee  于2019年8月23日周五 下午4:34写道:
>>> >
>>> >> Thanks for your reply @Zili.
>>> >> I'm afraid it's not the same issue.
>>> >> I found that the FlinkShell.class was not included in flink dist jar
>>> file
>>> >> in 1.9.0 version.
>>> >> Nowhere can find this class file inside jar, either in opt or lib
>>> >> directory under root folder of flink distribution.
>>> >>
>>> >>
>>> >> On Fri, Aug 23, 2019 at 4:10 PM Zili Chen 
>>> wrote:
>>> >>
>>> >>> Hi Gavin,
>>> >>>
>>> >>> I also find a problem in shell if the directory contain whitespace
>>> >>> then the final command to run is incorrect. Could you check the
>>> >>> final command to be executed?
>>> >>>
>>> >>> FYI, here is the ticket[1].
>>> >>>
>>> >>> Best,
>>> >>> tison.
>>> >>>
>>> >>> [1] https://issues.apache.org/jira/browse/FLINK-13827
>>> >>>
>>> >>>
>>> >>> Gavin Lee  于2019年8月23日周五 下午3:36写道:
>>> >>>
>>> >>>> Why bin/start-scala-shell.sh local return following error?
>>> >>>>
>>> >>>> bin/start-scala-shell.sh local
>>> >>>>
>>> >>>> Error: Could not find or load main class
>>> >>>> org.apache.flink.api.scala.FlinkShell
>>> >>>> For flink 1.8.1 and previous ones, no such issues.
>>> >>>>
>>> >>>> On Fri, Aug 23, 2019 at 2:05 PM qi luo  wrote:
>>> >>>>
>>> >>>>> Congratulations and thanks for the hard work!
>>> >>>>>
>>> >>>>> Qi
>>> >>>>>
>>> >>>>> On Aug 22, 2019, at 8:03 PM, Tzu-Li (Gordon) Tai <
>>> tzuli...@apache.org>
>>> >>>>> wrote:
>>> >>>>>
>>> >>>>> The Apache Flink community is very happy to announce the release of
>>> >>>>> Apache Flink 1.9.0, which is the latest major release.
>>> >>>>>
>>> >>>>> Apache Flink® is an open-source stream processing framework for
>>> >>>>> distributed, high-performing, always-available, and accurate data
>>> streaming
>>> >>>>> applications.
>>> >>>>>
>>> >>>>> The release is available for download at:
>>> >>>>> https://flink.apache.org/downloads.html
>>> >>>>>
>>> >>>>> Please check out the release blog post for an overview of the
>>> >>>>> improvements for this new major release:
>>> >>>>> https://flink.apache.org/news/2019/08/22/release-1.9.0.html
>>> >>>>>
>>> >>>>> The full release notes are available in Jira:
>>> >>>>>
>>> >>>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12344601
>>> >>>>>
>>> >>>>> We would like to thank all contributors of the Apache Flink
>>> community
>>> >>>>> who made this release possible!
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Gordon
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>> --
>>> >>>> Gavin
>>> >>>>
>>> >>>
>>> >>
>>> >> --
>>> >> Gavin
>>> >>
>>> >
>>>
>>> --
>>> Gavin
>>>
>>


Re: [SURVEY] How many people are using customized RestartStrategy(s)

2019-09-12 Thread Oytun Tez
Hi Zhu,

We are using custom restart strategy like this:

environment.setRestartStrategy(failureRateRestart(2, Time.minutes(1),
Time.minutes(10)));


---
Oytun Tez

*M O T A W O R D*
The World's Fastest Human Translation Platform.
oy...@motaword.com — www.motaword.com


On Thu, Sep 12, 2019 at 7:11 AM Zhu Zhu  wrote:

> Hi everyone,
>
> I wanted to reach out to you and ask how many of you are using a
> customized RestartStrategy[1] in production jobs.
>
> We are currently developing the new Flink scheduler[2] which interacts
> with restart strategies in a different way. We have to re-design the
> interfaces for the new restart strategies (so called
> RestartBackoffTimeStrategy). Existing customized RestartStrategy will not
> work any more with the new scheduler.
>
> We want to know whether we should keep the way
> to customized RestartBackoffTimeStrategy so that existing customized
> RestartStrategy can be migrated.
>
> I'd appreciate if you can share the status if you are using customized
> RestartStrategy. That will be valuable for use to make decisions.
>
> [1]
> https://ci.apache.org/projects/flink/flink-docs-master/dev/task_failure_recovery.html#restart-strategies
> [2] https://issues.apache.org/jira/browse/FLINK-10429
>
> Thanks,
> Zhu Zhu
>


Re: [DISCUSS] Create a Flink ecosystem website

2019-07-26 Thread Oytun Tez
I agree with Robert – localization (this is what we do at MotaWord) is a
maintenance work. If not maintained as well as mainstream, it will only
damage and distant devs that use those local websites.

Re: comments, I don't think people will really discuss furiously. But we at
least need a system where we understand the popularity of a package, it
helps to pick among similar packages if any. Something like the popularity
figure here that we can fetch from somewhere:
https://mvnrepository.com/popular

---
Oytun Tez

*M O T A W O R D*
The World's Fastest Human Translation Platform.
oy...@motaword.com — www.motaword.com


On Tue, Jul 23, 2019 at 5:07 AM Robert Metzger  wrote:

> Thanks a lot Marta for offering to write a blog post about the community
> site!
>
> I'm not sure if multi-language support for the site is a good idea. I see
> the packages site as something similar to GitHub or Jira. The page itself
> contains very view things we could actually translate. The package owners
> usually are only able to provide one or two languages for their package
> description.
> For the comments, we don't want disjoint discussions to happen.
>
> I've also kicked off a discussion with Apache legal on the initiative [1].
> We might not be able to host this at Apache, but let's see where the
> discussion goes.
>
>
> [1]
> https://lists.apache.org/thread.html/ee76a02257b51292ab61f6ac8d3d69307e83cc569cdeebde80596207@%3Clegal-discuss.apache.org%3E
>
>
> On Sat, Jul 20, 2019 at 5:25 AM Becket Qin  wrote:
>
>> [Sorry for the incomplete message. Clicked send by mistake...]
>>
>> I agree with Marta that it might be good to have multi-language support
>> as a mid-term goal.
>>
>> Jiangjie (Becket) Qin
>>
>> On Sat, Jul 20, 2019 at 11:22 AM Becket Qin  wrote:
>>
>>> The website is awesome! I really like its conciseness and yet fairly
>>> useful information and functionalities. I cannot think of much to improve
>>> at the moment. Just one thought, do we need an "others" category, just in
>>> case a package does not fit into any of the current given categories?
>>>
>>> Thanks Robert and Daryl for the great effort. Looking forward to seeing
>>> this get published soon!!
>>>
>>> I agree with Marta that
>>>
>>> Jiangjie (Becket) Qin
>>>
>>> On Sat, Jul 20, 2019 at 1:34 AM Marta Paes Moreira 
>>> wrote:
>>>
>>>> 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/pac