Re: Quick start guide

Hi, Yes, I think this is wrong in the doc and should refer to the TaskManager logs. Best, Aljoscha > On 4. Sep 2017, at 03:56, Michael Fong wrote: > > Hi, > > I was following the quick start guide on official documents >

[jira] [Created] (FLINK-7568) Bring window documentation up-to-date with latest changes and improve

Aljoscha Krettek created FLINK-7568: --- Summary: Bring window documentation up-to-date with latest changes and improve Key: FLINK-7568 URL: https://issues.apache.org/jira/browse/FLINK-7568 Project

[jira] [Created] (FLINK-7564) Fix Watermark semantics in Table API

Aljoscha Krettek created FLINK-7564: --- Summary: Fix Watermark semantics in Table API Key: FLINK-7564 URL: https://issues.apache.org/jira/browse/FLINK-7564 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-7563) Fix watermark semantics in CEP operators

Aljoscha Krettek created FLINK-7563: --- Summary: Fix watermark semantics in CEP operators Key: FLINK-7563 URL: https://issues.apache.org/jira/browse/FLINK-7563 Project: Flink Issue Type: Bug

Re: [DISCUSS] Watermark boundary condition

Hi, Excellent, thanks for pointing this out! The definition in Watermark.java, which is used by HeapInternalTimerService.java, WindowOperator.isWindowLate() and WindowOperator.isElementLate() and is also documented in [1] is the definitive (ha!) definition. I created Jira issues for fixing the

Re: [DISCUSS] Flink 1.4 and time based release

+1 On using "Fix Version" for that. I always try to use that already for things that need fixing in the next release. Also "Blocker" is a thing there. > On 30. Aug 2017, at 20:29, Eron Wright wrote: > > I definitely think the conversation must happen in the context of the > expected feature-set

[jira] [Created] (FLINK-7553) Use new SinkFunction interface in FlinkKafkaProducer010

Aljoscha Krettek created FLINK-7553: --- Summary: Use new SinkFunction interface in FlinkKafkaProducer010 Key: FLINK-7553 URL: https://issues.apache.org/jira/browse/FLINK-7553 Project: Flink

[jira] [Created] (FLINK-7552) Extend SinkFunction interface with SinkContext

Aljoscha Krettek created FLINK-7552: --- Summary: Extend SinkFunction interface with SinkContext Key: FLINK-7552 URL: https://issues.apache.org/jira/browse/FLINK-7552 Project: Flink Issue

Re: Sync Flink

Hi, This is not possible out-of-box, but you could use a ProcessFunction (or rather CoProcessFunction) to buffer elements and set a timer so that you only emit when the watermarks advances on both inputs. Best, Aljoscha > On 28. Aug 2017, at 08:10, ziv wrote: > > People, > > I have two so

Re: Serialization Issue

Hi, TypeInformationKeyValueSerializationSchema uses Flink TypeSerializers to serialize those Strings. What you're seeing is the binary representation of those Strings which, admittedly, resembles the original Strings. If you want to have the data in Kafka with real Strings, I think you need to

Re: [DISCUSS] Stop serving docs for Flink version prior to 1.0

+1 > On 22. Aug 2017, at 18:01, Stephan Ewen wrote: > > +1 > > On Tue, Aug 22, 2017 at 5:58 PM, Ufuk Celebi wrote: > >> Quick update: If there are no objections, I will start looking into >> how to stop serving the docs for Flink < 1.0 after tomorrow. >> >> >> On Wed, Aug 16, 2017 at 10:45 P

[jira] [Created] (FLINK-7480) Set HADOOP_CONF_DIR to sane default if not set

Aljoscha Krettek created FLINK-7480: --- Summary: Set HADOOP_CONF_DIR to sane default if not set Key: FLINK-7480 URL: https://issues.apache.org/jira/browse/FLINK-7480 Project: Flink Issue

[jira] [Created] (FLINK-7477) Use "hadoop classpath" to augment classpath when available

Aljoscha Krettek created FLINK-7477: --- Summary: Use "hadoop classpath" to augment classpath when available Key: FLINK-7477 URL: https://issues.apache.org/jira/browse/FLINK-7477 Proj

[jira] [Created] (FLINK-7442) Add option for using a child-first classloader for loading user code

Aljoscha Krettek created FLINK-7442: --- Summary: Add option for using a child-first classloader for loading user code Key: FLINK-7442 URL: https://issues.apache.org/jira/browse/FLINK-7442 Project

Re: Which branch should I build for Flink 1.3.2

Hi, The release-1.3 branch is the general 1.3.x branch from which we cut specific releases. You can build that to basically get the latest 1.3.x SNAPSHOT. If you specifically want to build 1.3.2 I suggest checking out the release-1.3.2 tag and building from that. Best, Aljoscha > On 12. Aug 20

Re: How to access HDFS file from flink

Hi, Unfortunately. Inline images do not work on these mailing lists. Also, could you please use the user mailing lists in the future, since the dev mailing lists are meant for discussing the development of Flink. Best, Aljoscha > On 11. Aug 2017, at 11:31, P. Ramanjaneya Reddy wrote: > > >

[jira] [Created] (FLINK-7414) Hardcode scala.version to 2.11 in flink-quickstart-scala

Aljoscha Krettek created FLINK-7414: --- Summary: Hardcode scala.version to 2.11 in flink-quickstart-scala Key: FLINK-7414 URL: https://issues.apache.org/jira/browse/FLINK-7414 Project: Flink

[jira] [Created] (FLINK-7413) Release Hadoop 2.8.x convenience binaries for 1.3.x

Aljoscha Krettek created FLINK-7413: --- Summary: Release Hadoop 2.8.x convenience binaries for 1.3.x Key: FLINK-7413 URL: https://issues.apache.org/jira/browse/FLINK-7413 Project: Flink

[jira] [Created] (FLINK-7398) Table API operators/UDFs must not store Logger

Aljoscha Krettek created FLINK-7398: --- Summary: Table API operators/UDFs must not store Logger Key: FLINK-7398 URL: https://issues.apache.org/jira/browse/FLINK-7398 Project: Flink Issue

[jira] [Created] (FLINK-7396) Don't put multiple directories in HADOOP_CONF_DIR in config.sh

Aljoscha Krettek created FLINK-7396: --- Summary: Don't put multiple directories in HADOOP_CONF_DIR in config.sh Key: FLINK-7396 URL: https://issues.apache.org/jira/browse/FLINK-7396 Project:

[ANNOUNCE] Apache Flink 1.3.2 released

The Apache Flink community is pleased to announce the release of Apache Flink 1.3.2. 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://flin

[RESULT][VOTE] Release 1.3.2, release candidate #3

otes, 5 binding. No 0 or -1 votes. > On 5. Aug 2017, at 07:49, Aljoscha Krettek wrote: > > Hi Bowen, > > You're right, I didn't give a lot of thought to Kinesis because there were > critical bugs in Kafka and incremental checkpointing that needed to be fixed

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

With 24 hours now having passed, this vote is now complete. I'll summarise the results in an extra thread. Best, Aljoscha > On 5. Aug 2017, at 07:49, Aljoscha Krettek wrote: > > Hi Bowen, > > You're right, I didn't give a lot of thought to Kinesis because there

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

- verified source and binary checksums > - verified LICENSEs > - verified NOTICEs > - built from source > > Greg > >> On Aug 4, 2017, at 2:00 AM, Aljoscha Krettek wrote: >> >> Hi everyone, >> >> Please review and vote on the release candidate #3 for the

Re: [VOTE] Release 1.3.2, release candidate #2

: > FLINK-7352 > > Should this be resolved for 1.3.2 ? > > Thanks > > On Sun, Jul 30, 2017 at 12:07 AM, Aljoscha Krettek > wrote: > >> Hi everyone, >> >> Please review and vote on the release candidate #2 for the version 1.3.2, >> as follows: >

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

gt;> - Cloud env: AWS >>> - Distributions: EMR 5.7.0 >>> - Flink deployment method: YARN (Hadoop 2.7.2) >>> - HA: enabled >>> - Kerberos: disabled >>> - Kafka version: 0.10, 0.11 >>> - State Backends: Heap (Sync / Async) & RocksDB (incremen

[VOTE] Release 1.3.2, release candidate #3

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

[CANCEL] [VOTE] Release 1.3.2, release candidate #2

amp; RocksDB (incremental / full) >> - Filesystem: S3 and HDFS (Hadoop 2.7.2) >> - Externalized checkpoints: enabled & disabled >> >> 2. Building with Scala 2.11 works >> >> 3. Building against Hadoop version works >> >> >>> Am 30.07.2017 u

[jira] [Created] (FLINK-7362) CheckpointProperties are not correctly set when restoring savepoint with HA enabled

Aljoscha Krettek created FLINK-7362: --- Summary: CheckpointProperties are not correctly set when restoring savepoint with HA enabled Key: FLINK-7362 URL: https://issues.apache.org/jira/browse/FLINK-7362

Re: [DISCUSS] Service Authorization (redux)

Hi Eron, I think after Dropping support for Java 7 we will move to Akka 2.4+, so we should be good there. I think quite some users should find a (more) secure Flink interesting. Best, Aljoscha > On 24. Jul 2017, at 03:11, Eron Wright wrote: > > Hello, now might be a good time to revisit an im

Re: KeyBy fields do not support java.lang.Array?

Hi, Which version of Flink are you using? This issue should have been resolved at least by 1.3.0: https://issues.apache.org/jira/browse/FLINK-5874 . Currently such keys should be rejected. There is also this issue, that aims to re-introduce prop

[VOTE] Release 1.3.2, release candidate #2

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

[CANCEL] [VOTE] Release 1.3.2, release candidate #1

Unfortunately, there is a typo in the quickstarts that makes them unusable out-of-box. I'm cancelling this RC and will create a new one immediately. Sorry for the inconvenience. Best, Aljoscha > On 29. Jul 2017, at 08:06, Aljoscha Krettek wrote: > > Hi everyone, > > Pl

[VOTE] Release 1.3.2, release candidate #1

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

Re: [ANNOUNCE] New Flink PMC member: Chesnay Schepler

Well deserved! Congrats. :-) > On 28. Jul 2017, at 17:45, Tzu-Li (Gordon) Tai wrote: > > Congrats Chesnay! > > On Fri, Jul 28, 2017 at 11:40 PM, Matthias J. Sax wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> Congrats! >> >> On 7/28/17 4:40 PM, Fabian Hueske wrote: >>>

Re: [DISCUSS] Release 1.3.2 planning

rs, > Gordon > > On 28 July 2017 at 8:39:05 PM, Aljoscha Krettek (aljos...@apache.org) wrote: > > I think we don't have to consider that since no-one (aside from testing) ever > ran into problems with that. However, we should keep in mind merging this for > 1.4 (and 1.3

Re: [DISCUSS] Release 1.3.2 planning

ackwards compatibility). > > What do you think? > > - Gordon > On 25 July 2017 at 11:02:05 PM, Aljoscha Krettek (aljos...@apache.org) wrote: > > I did some preliminary cluster testing on 1.3-SNAPSHOT and it seems there is > another issue in RocksDB with incremental checkp

[jira] [Created] (FLINK-7290) Make release scripts modular

Aljoscha Krettek created FLINK-7290: --- Summary: Make release scripts modular Key: FLINK-7290 URL: https://issues.apache.org/jira/browse/FLINK-7290 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-7281) Fix various issues in (Maven) release infrastructure

Aljoscha Krettek created FLINK-7281: --- Summary: Fix various issues in (Maven) release infrastructure Key: FLINK-7281 URL: https://issues.apache.org/jira/browse/FLINK-7281 Project: Flink

Re: [VOTE] Release Apache Flink-shaded 1.0 (RC2)

+1 - I checked the signatures and sha/md5 sums. - I verified that the published jars only contain the shaded code that they should contain > On 24. Jul 2017, at 17:43, Chesnay Schepler wrote: > > Dear Flink community, > > Please vote on releasing the following candidate as Apache Flink-shad

Re: [DISCUSS] Release testing procedures, Flink 1.3.2

;> wrote: >> >>> Hi, >>> >>> Regarding Kafka at-least-once bug. I could try to play with Flink 1.3.1 on >>> a real cluster to provoke this bug, by basically repeating >>> KafkaProducerTestBase#testOneToOneAtLeastOnce on a larger scale. >>

[jira] [Created] (FLINK-7268) Zookeeper Checkpoint Store interacting with Incremental State Handles can lead to loss of handles

Aljoscha Krettek created FLINK-7268: --- Summary: Zookeeper Checkpoint Store interacting with Incremental State Handles can lead to loss of handles Key: FLINK-7268 URL: https://issues.apache.org/jira/browse/FLINK

Re: [DISCUSS] Release 1.3.2 planning

2017, at 14:39, Timo Walther wrote: > > I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are > resolved from the Table & SQL API side. > > Regards, > Timo > > Am 24.07.17 um 11:14 schrieb Aljoscha Krettek: >> @Greg: I merged that. >&g

Re: [DISCUSS] Release 1.3.2 planning

gt;> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen...@offerupnow.com) wrote: >> >> Hi Aljoscha, >> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed >> in 1.3.2, if it makes sense. >> >> Thanks, >> Bowen >>

[jira] [Created] (FLINK-7241) Fix YARN high availability documentation

Aljoscha Krettek created FLINK-7241: --- Summary: Fix YARN high availability documentation Key: FLINK-7241 URL: https://issues.apache.org/jira/browse/FLINK-7241 Project: Flink Issue Type: Bug

Re: [DISCUSS] Release testing procedures, Flink 1.3.2

production verification as well. > > Regards, > Shaoxuan > > > On Wed, Jul 19, 2017 at 9:11 PM, Aljoscha Krettek > wrote: > >> Hi Everyone, >> >> We are on the verge of starting the release process for Flink 1.3.2 and >> there have been some cr

[DISCUSS] Release testing procedures, Flink 1.3.2

Hi Everyone, We are on the verge of starting the release process for Flink 1.3.2 and there have been some critical issues in both Flink 1.3.0 and 1.3.1. For Flink 1.3.2 I want to make very sure that we test as much as possible. For this I’m proposing a slightly changed testing procedure [1]. Th

Re: Request for contributor permissions

Hi, I added you to the list of contributors. Welcome to the community! :-) Best, Aljoscha > On 13. Jul 2017, at 16:16, 周思华 wrote: > > Hi devs, > I'm very interested in Flink and willing to contribute to it. Cloud anybody > give me the contributor permissions? My jira username is "sihuazhou".

Re: Feel confused for the illustration of tumbling window

So it is not clear to which window they would belong. >> >> 2017-07-13 12:03 GMT+02:00 Aljoscha Krettek : >> >>> Hi, >>> >>> How do you mean? The windows in the illustration are not overlapping. >>> >>> I’m very happy about suggestio

Re: Feel confused for the illustration of tumbling window

Hi, How do you mean? The windows in the illustration are not overlapping. I’m very happy about suggestions for improving this, though, if anyone has one. 😃 Best, Aljoscha > On 13. Jul 2017, at 11:43, jincheng sun wrote: > > Hi guys, > Feel confused for the illustration of tumbling window,

Re: Re: [DISCUSS] FLIP-22: Eager State Declaration

provided by a user who then >> registers all the state descriptors he has. >> >> >> On 04.07.2017 20:00, Tzu-Li (Gordon) Tai wrote: >> >>> Hi Flink devs! >>> >>> I would like to propose the following FLIP - Eager State Declaration for

Re: [DISCUSS] Release 1.3.2 planning

please update the Jira issues that they think should be release blocking. I would like to start building release candidates at the end of this week, if possible. And yes, I’m volunteering to be the release manager on this release. ;-) Best, Aljoscha > On 7. Jul 2017, at 16:03, Aljoscha Krett

[jira] [Created] (FLINK-7164) Extend integration tests for (externalised) checkpoints, checkpoint store

Aljoscha Krettek created FLINK-7164: --- Summary: Extend integration tests for (externalised) checkpoints, checkpoint store Key: FLINK-7164 URL: https://issues.apache.org/jira/browse/FLINK-7164

Re: [DISCUSS] Release 1.3.2 planning

s: FLINK-7069 and FLINK-6965. > > FLINK-7069 is being merged and we have a PR for FLINK-6965. > > ~Haohui > > On Thu, Jul 6, 2017 at 1:44 AM Aljoscha Krettek wrote: > >> I’m seeing these remaining blockers: >> https://issues.apache.org/jira/browse/FLINK-7069?filte

[jira] [Created] (FLINK-7133) Fix Elasticsearch version interference

Aljoscha Krettek created FLINK-7133: --- Summary: Fix Elasticsearch version interference Key: FLINK-7133 URL: https://issues.apache.org/jira/browse/FLINK-7133 Project: Flink Issue Type: Bug

Re: [DISCUSS]refactor StreamConfig

Hi, Yes, that sounds very good! I like the idea of having an interface that is a view on some of the settings. We could maybe improve the naming, because to me it is not completely clear what the difference between OperatorSettings and OperatorProperties is (I mean just the name, the functional

Re: How to set jobmanager.rpc.address in TaskManger node in HA cluster

Cool, thanks for letting us know that you figured it out and what it was! > On 7. Jul 2017, at 05:52, Mu Kong wrote: > > Sorry. I didn't put high-availability: zookeeper in taskmangers' > flink-config.yml. > After I fixed this, everything went well. > > On Fri, Jul 7, 2017 at 11:08 AM, Mu Kong

Re: refactor StreamConfig

need to be serialized >> into the Configuration, which is underlying before and flows across modules. >> >> >> Do you agree what I understand? >> >> >> Best Regards! >> >> >> Xu Pingyong >> >> >> >> >> >> >>

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

+1 This sounds very good! I just hope that everyone is aware enough and doesn’t forget adding these tags. > On 6. Jul 2017, at 09:59, Tzu-Li (Gordon) Tai wrote: > > > Hi devs, > > I would like to follow up my proposal in [1] regarding how we can more > systematically and easily collect brea

Re: [DISCUSS] Release 1.3.2 planning

> https://issues.apache.org/jira/browse/FLINK-6996. > > Cheers, > Gordon > On 30 June 2017 at 12:46:07 AM, Aljoscha Krettek (aljos...@apache.org) wrote: > > Gordon and I found this (in my opinion) blocking issue: > https://issues.apache.org/jira/browse/FLINK-7041 > &l

Re: connect data stream with parameter stream

Hi Lei, I’m afraid there is currently no API for doing this in one operation. I see two options right now: 1. Built a custom operator that implements windowing and also has a second input for the parameter stream. This would be a subclass of TwoInputStreamOperator. As an example, you can look

Re: refactor StreamConfig

Hi, Yes, but I think what Stephan was hinting at was to change both of them to be serialisable when already working on this. I think input serialiser is fine to have in OperatorConfig, you’re right! I don’t see getChainIndex() used anywhere in the code, though. And the output edges and seriali

Re: refactor StreamConfig

I think the proposed changed are good, I just wanted to make sure that they don’t interfere with what other people are doing. I also proposed these steps on the Github PR: Also, for actually doing the changes I suggest separate steps, i.e. separate commits. With possibly separate PRs to make rev

Re: Tips to fix IDEA strange problem after updating master code

Thanks for the hint! > On 4. Jul 2017, at 06:03, Ted Yu wrote: > > Looks like the picture didn't go thru. > > Mind using third party site ? > > Thanks > > On Mon, Jul 3, 2017 at 8:56 PM, Jark Wu wrote: > >> Hi devs, >> >> Yesterday, I updated the master code which include [FLINK-7030]: Bui

Re: [DISCUSS] First release of flink-shaded

following: > > import com.esotericsoftware.kryo.Serializer; > > I think shading is possible since we can declare the Serializer class to > come from shaded Kryo namespace. > > On Mon, Jul 3, 2017 at 9:25 AM, Aljoscha Krettek > wrote: > >> Is it even possible to sha

Re: [DISCUSS] First release of flink-shaded

Is it even possible to shade Kryo with it being in the public API? I don’t think it is (without looking into this to deeply, though). > On 3. Jul 2017, at 17:23, Chesnay Schepler wrote: > > I would tackle Kryo later as it is exposed through the API > (StreamExecutionEnvironment#addDefaultKryoS

Re: [DISCUSS] First release of flink-shaded

+1 Sounds good! I have followed the process on the various issues and the new shaded repository and the changes seem straightforward (more or less ;-)) > On 3. Jul 2017, at 14:32, Chesnay Schepler wrote: > > Hello, > > I would like to kick off the first release of flink-shaded. > > In the cu

Re: [DISCUSS] Release 1.3.2 planning

Gordon and I found this (in my opinion) blocking issue: https://issues.apache.org/jira/browse/FLINK-7041 I’m trying to quickly provide a fix. > On 26. Jun 2017, at 15:30, Timo Walther wrote: > > I just opened a PR which should be included in

[jira] [Created] (FLINK-7041) Deserialize StateBackend from JobCheckpointingSettings with user classloader

Aljoscha Krettek created FLINK-7041: --- Summary: Deserialize StateBackend from JobCheckpointingSettings with user classloader Key: FLINK-7041 URL: https://issues.apache.org/jira/browse/FLINK-7041

Re: [DISCUSS] FLIP-21 - Improve object Copying/Reuse Mode for Streaming Runtime

+1 for changing the default if so many people encountered problems with serialisation costs. The first two modes don’t require any code changes, correct? Only the last one would require changes to the stream input processors. We should also keep this issue in mind: https://issues.apache.org/ji

Re: Switch to Scala 2.11 as a default build profile

+1 For changing the default. I think a lot of systems don’t even support 2.10 anymore. > On 28. Jun 2017, at 14:38, Ted Yu wrote: > > +1 on using Scale 2.11 as default. > Original message From: Piotr Nowojski > Date: 6/28/17 5:36 AM (GMT-08:00) To: > dev@flink.apache.org

Reduced Availability from 17.6. - 24.6

Hi, I’ll be on vacation next week, just in case anyone is wondering why I’m not responding. :-) Best, Aljoscha

Re: Tracking API

n invocation of > submitTask function. I think the stack trace will not tell me that because > they are in different thread contexts. > > Regards, > Ameet > > On Thu, Jun 15, 2017 at 3:16 PM, Aljoscha Krettek > wrote: > >> Hi, >> >> Would this be what

Re: Tracking API

Hi, Would this be what you’re looking for: https://stackoverflow.com/questions/1069066/get-current-stack-trace-in-java ? Best, Aljoscha > On 14. Jun 2017, at 12:46, Ameet BD wrote: > > Hello, > > I am trying to pr

Re: [DISCUSS] Release Apache Flink 1.3.1

; >> 2017-06-13 14:03 GMT+08:00 Tzu-Li (Gordon) Tai : >> >>> I’ve just merged the last blockers for 1.3.1. IMO, the release process for >>> 1.3.1 is ready for kick off. >>> >>> >>> On 8 June 2017 at 10:32:47 AM, Aljoscha Krettek

Re: [DISCUSS] Removal of twitter-inputformat

Bumpety-bump. I would be in favour or removing this: - It can be implemented as a MapFunction parser after a TextInputFormat - Additions, changes, fixes that happen on TextInputFormat are not reflected to SimpleTweetInputFormat - SimpleTweetInput format overrides nextRecord(), which is not som

Re: FlinkML on slack

Thanks! > On 8. Jun 2017, at 11:21, Stavros Kontopoulos > wrote: > > Hi Aljoscha, > > Slack is invite only to the best of my knowledge, I just sent you an > invitation. > > Best, > Stavros > > > On Thu, Jun 8, 2017 at 11:31 AM, Aljoscha Krettek

Re: [DISCUSS] Release Apache Flink 1.3.1

ill > > On Wed, Jun 7, 2017 at 4:59 PM, Aljoscha Krettek > wrote: > >> I would also like to raise another potential blocker: it’s currently not >> easily possible for users to start a job in local mode in the IDE and to >> then interact with that cluster, say for expe

Re: FlinkML on slack

Hi, Is the slack invite based? If yes, could you please send me one? Best, Aljoscha > On 7. Jun 2017, at 21:56, Stavros Kontopoulos > wrote: > > Hi all, > > We took the initiative to create the organization for FlinkML on slack > (thnx Eron). > There is now a channel for model-serving >

Re: [DISCUSS] Release Apache Flink 1.3.1

I would also like to raise another potential blocker: it’s currently not easily possible for users to start a job in local mode in the IDE and to then interact with that cluster, say for experimenting with queryable state. At least one user walked into this problem already with the 1.3.0 RC: ht

Re: Building only flink-java8 module

. >>>> Just an example: >>>> >>>> >>>> >>>> 16:12:53,103 INFO >>>> org.apache.flink.runtime.taskmanager.TaskManagerRegistrationTest -

Re: Building only flink-java8 module

the command given by Aljoscha, I got: >> >> https://pastebin.com/8WTGvdFQ >> >> FYI >> >> On Thu, Jun 1, 2017 at 8:17 AM, Aljoscha Krettek >> wrote: >> >>> Hi, >>> >>> I think you can use something like >>> >

Re: Building only flink-java8 module

Hi, I think you can use something like mvn verify -am -pl flink-java8 (From the base directory) The -pl flag will tell maven to only do that module while -am tells it to also builds its dependencies. This might or might not also run the tests on the dependent-upon projects, I’m not sure. As

Re: [VOTE] Release Apache Flink 1.3.0 (RC3)

Yes, FLINK-6783 might even have been a release blocker…. It’s a new feature that simply doesn’t work in most cases. > On 31. May 2017, at 14:51, Timo Walther wrote: > > We should also include FLINK-6783. It seems that WindowedStream::aggregate is > broken right now. > > > Am 31.05.17 um 14:3

Re: [VOTE] Release Apache Flink 1.3.0 (RC3)

+1 I did: - manually check the release using the new end-to-end tests: https://github.com/apache/flink/pull/3911 . - verify that the source builds - Check the (transitive) dependencies of flink-dist compared to 1.2.x. The new deps are: com.squareup.

Re: [DISCUSS] Backwards compatibility policy.

Normally, I’m the first one to suggest removing everything that is not absolutely necessary in order to have a clean code base. On this issue, though, I think we should support restoring from old Savepoints as far back as possible if it does not make the code completely unmaintainable. Some user

Re: ListState to List

Hi, The interface is restrictive on purpose because depending on the state backend it might not be possible to provide a List-like interface. There might be state backends that stream in the list from somewhere else or other restrictions. If we now allowed a more general interface here we would

[jira] [Created] (FLINK-6539) Add automated end-to-end tests

Aljoscha Krettek created FLINK-6539: --- Summary: Add automated end-to-end tests Key: FLINK-6539 URL: https://issues.apache.org/jira/browse/FLINK-6539 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-6515) KafkaConsumer checkpointing fails because of ClassLoader issues

Aljoscha Krettek created FLINK-6515: --- Summary: KafkaConsumer checkpointing fails because of ClassLoader issues Key: FLINK-6515 URL: https://issues.apache.org/jira/browse/FLINK-6515 Project: Flink

[jira] [Created] (FLINK-6514) Cannot start Flink Cluster in standalone mode

Aljoscha Krettek created FLINK-6514: --- Summary: Cannot start Flink Cluster in standalone mode Key: FLINK-6514 URL: https://issues.apache.org/jira/browse/FLINK-6514 Project: Flink Issue Type

Re: [DISCUSS] What is a "Blocker" in our JIRA?

IMHO, the problem with the “add documentation” issues is that they should ideally have been documented as part of the feature development. (Full disclosure: I’m not innocent there and the Per-Key Window State Doc is somewhat my fault.) Sometimes, though, several features are developed over the c

Re: Examples of Flink windowing unit tests, and option to bring in flink-spector to Flink

able law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations

Re: Examples of Flink windowing unit tests, and option to bring in flink-spector to Flink

Hi, Yes, unfortunately there are no good unit test examples for testing Flink jobs (with windowing or without). And yes, I would like to have something like flink-spector (or flink-spector) as part of Flink as the promoted way of doing Job testing. In my opinion this is blocked on a good way of

Re: [DISCUSS] Feature Freeze

TypeSerializers: https:// >>>>> github.com/apache/flink/pull/3804 >>>>> PR #2 (will open soon) integrate serializer reconfiguration into state >>>>> restore flow (FLINK-6425) >>>>> >>>>> 2. Major new functionality

[jira] [Created] (FLINK-6427) BucketingSink does not sync file length in case of cancel

Aljoscha Krettek created FLINK-6427: --- Summary: BucketingSink does not sync file length in case of cancel Key: FLINK-6427 URL: https://issues.apache.org/jira/browse/FLINK-6427 Project: Flink

Re: Question on checkpointing

Hi Blake, I didn’t see any mails on the user mailing list regarding this. Is it still relevant. From the looks of it you might be interested in the savepoints feature: https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/savepoints.html

[jira] [Created] (FLINK-6413) Add stream operator callback to notify about consumed network buffer

Aljoscha Krettek created FLINK-6413: --- Summary: Add stream operator callback to notify about consumed network buffer Key: FLINK-6413 URL: https://issues.apache.org/jira/browse/FLINK-6413 Project

Re: [DISCUSS] Feature Freeze

jira/browse/FLINK-6398 > > On Fri, Apr 28, 2017 at 11:48 AM, Aljoscha Krettek > wrote: > >> I think there might be a typo. We haven’t yet reached issue number 6389, >> if I’m not mistaken. The latest as I’m writing this is 6410. >> >>> On 28. Apr 2017, at 10:

Re: [DISCUSS] Feature Freeze

I think there might be a typo. We haven’t yet reached issue number 6389, if I’m not mistaken. The latest as I’m writing this is 6410. > On 28. Apr 2017, at 10:00, Flavio Pompermaier wrote: > > If it's not a problem it will be great for us to include also FLINK-6398 >

Re: [DISCUSS] Code style / checkstyle

rging it. > > On 18.04.2017 20:39, Aljoscha Krettek wrote: >> I rebased the PR [1] on current master. Is there any strong objection >> against merging this (minus the two last commits which introduce >> curly-brace-style checking). If not, I would like to merge this after tw

<    3   4   5   6   7   8   9   10   11   12   >