[jira] [Created] (FLINK-6607) Confusing statement in docs that Kafka 010 consumer does not require timestamp extractors

Tzu-Li (Gordon) Tai created FLINK-6607: -- Summary: Confusing statement in docs that Kafka 010 consumer does not require timestamp extractors Key: FLINK-6607 URL:

ListState to List

Hi, I would like to work with ListState, more specifically I would need to access the contents and sort them. For this I would need a collection type (e.g., the List, Array...). However, I see that if I have a variable of type <> the only interfaces I have are: state.get -> which returns an

[jira] [Created] (FLINK-6606) Create checkpoint hook with user classloader

Eron Wright created FLINK-6606: --- Summary: Create checkpoint hook with user classloader Key: FLINK-6606 URL: https://issues.apache.org/jira/browse/FLINK-6606 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-6605) Allow users to specify a default name for processing time

Haohui Mai created FLINK-6605: - Summary: Allow users to specify a default name for processing time Key: FLINK-6605 URL: https://issues.apache.org/jira/browse/FLINK-6605 Project: Flink Issue

Re: questions about Flink's HashJoin performance

Hi! Be aware that the "Row" and "Record" types are not very high performance data types. You might be measuring the data type overhead, rather than the hash table performance. Also, the build measurements include the data generation, which influences the results. If you want to purely benchmark

Re: Official Flink Docker images

How hard would it be to integrate the docker images into the Flink release process? Ideally, we could provide something like a staging directory for the docker images, so that we can include them into the vote. Once the vote has passed, the images will be made public through docker hub and

Flink issue

Hi, I'm running flink in a yarn session, and when a try to cancel a running program with parameters "-yid" and "job id", the flink job state remains in canceling mode and the resources remains occupied. A similar issue at

Re: [DISCUSS] Release 1.3.0 RC1 (Non voting, testing release candidate)

I totally forgot to post a document with testing tasks in the RC0 thread, so I'll do it in the RC1 thread. Please use this document: https://docs.google.com/document/d/11WCfV15VwQNF-Rar4E0RtWiZw1ddEbg5WWf4RFSQ_2Q/edit# If I have the feeling that not enough people are seeing the document, I'll

[jira] [Created] (FLINK-6604) Remove Java Serialization from the CEP library.

Kostas Kloudas created FLINK-6604: - Summary: Remove Java Serialization from the CEP library. Key: FLINK-6604 URL: https://issues.apache.org/jira/browse/FLINK-6604 Project: Flink Issue Type:

[jira] [Created] (FLINK-6603) Enable checkstyle on test sources

Greg Hogan created FLINK-6603: - Summary: Enable checkstyle on test sources Key: FLINK-6603 URL: https://issues.apache.org/jira/browse/FLINK-6603 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-6602) Table source with defined time attributes allows empty string

Timo Walther created FLINK-6602: --- Summary: Table source with defined time attributes allows empty string Key: FLINK-6602 URL: https://issues.apache.org/jira/browse/FLINK-6602 Project: Flink

[jira] [Created] (FLINK-6601) Use time indicators in DataStreamLogicalWindowAggregateRule

Timo Walther created FLINK-6601: --- Summary: Use time indicators in DataStreamLogicalWindowAggregateRule Key: FLINK-6601 URL: https://issues.apache.org/jira/browse/FLINK-6601 Project: Flink

[jira] [Created] (FLINK-6600) Add key serializer's config snapshot to KeyedBackendSerializationProxy

Tzu-Li (Gordon) Tai created FLINK-6600: -- Summary: Add key serializer's config snapshot to KeyedBackendSerializationProxy Key: FLINK-6600 URL: https://issues.apache.org/jira/browse/FLINK-6600

Re: Static deployment scheme for failure scenario

Hi Niklas, the current Scheduler implementation is designed with location transparency in mind. Tasks can express a location preference which is currently based on location constraints wrt other tasks. However, the community is thinking about enhancing the scheduling logic such that it can

Re: Official Flink Docker images

Great to hear Ismaël. This will make running Flink even easier :-) Cheers, Till On Tue, May 16, 2017 at 1:38 PM, Ismaël Mejía wrote: > As a follow up for this thread, the docker official images are out > since last week ago so you please guys go ahead and try them. The blog

[jira] [Created] (FLINK-6599) Communicate last committed checkpoint through trigger checkpoint message

Stefan Richter created FLINK-6599: - Summary: Communicate last committed checkpoint through trigger checkpoint message Key: FLINK-6599 URL: https://issues.apache.org/jira/browse/FLINK-6599 Project:

Re: Official Flink Docker images

As a follow up for this thread, the docker official images are out since last week ago so you please guys go ahead and try them. The blog post that presents them was published today. https://flink.apache.org/news/2017/05/16/official-docker-image.html On Sun, May 7, 2017 at 3:51 PM, Ismaël Mejía

[jira] [Created] (FLINK-6598) Fix `DataStreamGroupAggregateRule` matches error.

sunjincheng created FLINK-6598: -- Summary: Fix `DataStreamGroupAggregateRule` matches error. Key: FLINK-6598 URL: https://issues.apache.org/jira/browse/FLINK-6598 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-6597) Cleanup WindowOperatorTest useless imports

sunjincheng created FLINK-6597: -- Summary: Cleanup WindowOperatorTest useless imports Key: FLINK-6597 URL: https://issues.apache.org/jira/browse/FLINK-6597 Project: Flink Issue Type: Test

Re: questions about Flink's HashJoin performance

Thanks for all your enthusiastic response. Yes, My target was to try to find the best performance in memory. I got that. On Tue, 16 May 2017 at 4:10 PM Fabian Hueske wrote: > Hi, > > Flink's HashJoin implementation was designed to gracefully handle inputs > that exceed the

Re: questions about Flink's HashJoin performance

Hi, Flink's HashJoin implementation was designed to gracefully handle inputs that exceed the main memory. It is not explicitly optimized for in-memory processing and does not play fancy tricks like optimizing cache accesses or batching. I assume your benchmark is about in-memory joins only. This

Re: [DISCUSS] Release 1.3.0 RC1 (Non voting, testing release candidate)

Thanks for the pointer. I'll keep an eye on the JIRA. I've gone through the JIRAs tagged with 1.3.0 yesterday to create a list of new features in 1.3. Feel free to add more / change it in the wiki:

[jira] [Created] (FLINK-6596) Disable javadoc generation in all travis builds

Chesnay Schepler created FLINK-6596: --- Summary: Disable javadoc generation in all travis builds Key: FLINK-6596 URL: https://issues.apache.org/jira/browse/FLINK-6596 Project: Flink Issue