[jira] [Created] (FLINK-9941) Flush in ScalaCsvOutputFormat before close method

Rannn Tao created FLINK-9941: Summary: Flush in ScalaCsvOutputFormat before close method Key: FLINK-9941 URL: https://issues.apache.org/jira/browse/FLINK-9941 Project: Flink Issue Type:

[jira] [Created] (FLINK-9940) File source continuous monitoring mode: S3 files sometimes missed

Huyen Levan created FLINK-9940: -- Summary: File source continuous monitoring mode: S3 files sometimes missed Key: FLINK-9940 URL: https://issues.apache.org/jira/browse/FLINK-9940 Project: Flink

Re: is Flink's recovery speed still slow?

As far as I learned from folks with better understanding than myself , barrier alignment might be only path to get deterministic output. Any state or outcome between barrier alignments requires second thought(like UDP packages from network). Currently, alignment is used only do heavyweight

Re: Intro

Hi Kevin, Welcome! As a supplement to vino, Flink has a user list u...@flink.apache.org, which you can subscribe by sending a e-mail to user-subscr...@flink.apache.org Best, tison. vino yang 于2018年7月25日周三 上午10:01写道： > Hi Kevin, > > Welcome, I think you should read the offiicial documentation

Re: Intro

Hi Kevin, Welcome, I think you should read the offiicial documentation to know more about Flink community.[1] And you can read this documentation to learn how to contribute.[2] [1]: http://flink.apache.org/community.html [2]: http://flink.apache.org/how-to-contribute.html Thanks, vino.

Re: is Flink's recovery speed still slow?

Hi jiaxl, The paper you mentioned was published at 2017. I think it doesn't have much reference value now. Over time, both frameworks are constantly evolving. At the end of May this year, Flink has supported the major feature of local recovery in the latest release of version 1.5. This greatly

Intro

Hi Dev, New to Flink, coming from Metron use. Looking forward to using, and getting involved in the documentation of Flink. Who heads up the docs? Is there another list or use the user or community lists? Thanks, Kev

[jira] [Created] (FLINK-9939) Mesos: Not setting TMP dirs causes NPE

Gary Yao created FLINK-9939: --- Summary: Mesos: Not setting TMP dirs causes NPE Key: FLINK-9939 URL: https://issues.apache.org/jira/browse/FLINK-9939 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-9938) State TTL cleanup during full state scan upon checkpointing

Andrey Zagrebin created FLINK-9938: -- Summary: State TTL cleanup during full state scan upon checkpointing Key: FLINK-9938 URL: https://issues.apache.org/jira/browse/FLINK-9938 Project: Flink

Re: Backwards compatibility for REST API

Looked some more into it, as of _right now_ a 1.5.X client will not work against 1.6.0 cluster since the submission body was extended. But we could add a guard against this. On 24.07.2018 17:27, Chesnay Schepler wrote: Note that the changes made to the REST API will in the long-term reduce

Re: Backwards compatibility for REST API

Note that the changes made to the REST API will in the long-term reduce friction between versions, as we no longer have to submit data through the blob service, which is another internal API. On 24.07.2018 17:25, Chesnay Schepler wrote: /Will it be possible to submit a job graph built by 1.5.1

Re: Backwards compatibility for REST API

/Will it be possible to submit a job graph built by 1.5.1 client (that does not contain any connectors or operators that depend on internal API) to 1.6.x job manager?/ Probably yes, but generally there's no guarantee. The JobGraph is not a public API and thus may change in ways that could

is Flink's recovery speed still slow?

>From conclusion of this paper https://dl.acm.org/citation.cfm?id=3132750 , Flink's recovery speed is slower than that of Spark Streaming, which will be a problem in large scale deployment where fault happens frequently. I'd like to know

Re: Backwards compatibility for REST API

I would expect more external dependencies on the REST API and suggest to consider versioning and compatibility guarantees. The particular issue is from Beam and tracked here: https://issues.apache.org/jira/browse/BEAM-4842 I would be surprised if that is the only instance besides Flink CLI

Re: Backwards compatibility for REST API

Effectively there are no guarantees for backwards compatibility, although we try to maintain it. There are plans to version the REST API (https://issues.apache.org/jira/browse/FLINK-7551) but no definitive timeline. The change you mentioned in particular primarily affects internal code

Backwards compatibility for REST API

Hi, Are there any compatibility guarantees for the Flink REST API or plans to establish the same? I'm asking since I noticed that the 1.5.1 release has an incompatible change that prevents a 1.5.0 client to submit a job to 1.5.0 server (FLINK-9280, removed endpoint /blobserver/port). Such

[ANNOUNCE] Weekly community update #30

Dear community, this is the weekly community update thread #30. Please post any news and updates you want to share with the community to this thread. # First RC for Flink 1.6.0 The community is published the first release candidate for Flink 1.6.0 [1]. Please help the community by trying the RC

Re: [VOTE] Release 1.5.2, release candidate #1

correction: the correct link for [2]: https://dist.apache.org/repos/dist/dev/flink/flink-1.5.2/ On 24.07.2018 14:43, Chesnay Schepler wrote: Hi everyone, Please review and vote on the release candidate #3 for the version 1.5.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve

[VOTE] Release 1.5.2, release candidate #1

Hi everyone, Please review and vote on the release candidate #3 for the version 1.5.2, 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

[jira] [Created] (FLINK-9937) Kubernetes(Minikube) Flink : cannot submit job in Flink UI with FLink 1.5.1

Aleksandr Filichkin created FLINK-9937: -- Summary: Kubernetes(Minikube) Flink : cannot submit job in Flink UI with FLink 1.5.1 Key: FLINK-9937 URL: https://issues.apache.org/jira/browse/FLINK-9937

[jira] [Created] (FLINK-9936) Mesos resource manager unable to connect to master after failover

Renjie Liu created FLINK-9936: - Summary: Mesos resource manager unable to connect to master after failover Key: FLINK-9936 URL: https://issues.apache.org/jira/browse/FLINK-9936 Project: Flink

[jira] [Created] (FLINK-9935) Batch Table API: grouping by window and attribute causes java.lang.ClassCastException:

Roman Wozniak created FLINK-9935: Summary: Batch Table API: grouping by window and attribute causes java.lang.ClassCastException: Key: FLINK-9935 URL: https://issues.apache.org/jira/browse/FLINK-9935

[jira] [Created] (FLINK-9934) Kafka table source factory produces invalid field mapping

Timo Walther created FLINK-9934: --- Summary: Kafka table source factory produces invalid field mapping Key: FLINK-9934 URL: https://issues.apache.org/jira/browse/FLINK-9934 Project: Flink Issue

[jira] [Created] (FLINK-9933) Simplify taskmanager memory default values

Chesnay Schepler created FLINK-9933: --- Summary: Simplify taskmanager memory default values Key: FLINK-9933 URL: https://issues.apache.org/jira/browse/FLINK-9933 Project: Flink Issue Type:

[VOTE] Release 1.6.0, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 1.6.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], *

[jira] [Created] (FLINK-9932) If task executor offer slot to job master timeout the first time, the slot will leak

shuai.xu created FLINK-9932: --- Summary: If task executor offer slot to job master timeout the first time, the slot will leak Key: FLINK-9932 URL: https://issues.apache.org/jira/browse/FLINK-9932 Project: