RE: [ANNOUNCE] Welcome Jark Wu and Kostas Kloudas as committers

Congrats Jark and Kostas. Regards Ram -Original Message- From: Kostas Kloudas [mailto:k.klou...@data-artisans.com] Sent: Monday, February 13, 2017 3:06 PM To: dev@flink.apache.org Subject: Re: [ANNOUNCE] Welcome Jark Wu and Kostas Kloudas as committers Thanks a lot guys! Looking

RE: [ANNOUNCE] Welcome Stefan Richter as a new committer

Congrats Stefan Richter. Regards Ram -Original Message- From: Stefan Richter [mailto:s.rich...@data-artisans.com] Sent: Monday, February 13, 2017 2:50 PM To: dev@flink.apache.org Cc: u...@flink.apache.org; srich...@apache.org Subject: Re: [ANNOUNCE] Welcome Stefan Richter as a new

[jira] [Created] (FLINK-5813) code generation for user-defined aggregate functions

Shaoxuan Wang created FLINK-5813: Summary: code generation for user-defined aggregate functions Key: FLINK-5813 URL: https://issues.apache.org/jira/browse/FLINK-5813 Project: Flink Issue

Re: [DISCUSS] Table API / SQL indicators for event and processing time

Thanks everybody for the comments. Actually, I think we do not have much choice when deciding whether to use attributes or functions. Consider the following join query: SELECT​ ​t1.amount​,​ ​t2.rate FROM​ ​ table1 ​AS​ t1, ​ ​ table2 ​AS​ ​t2 WHERE ​ t1.currency = t2.currency AND

Flink Job Exception

Hi All, I'm trying to run a streaming job with flink 1.2 version and there are 3 task managers with 12 task slots. Irrespective of the parallelism that I give it always fails with the below error and I found a JIRA link corresponding to this issue. Can I know by when this will be resolved since

Reliable Distributed FS support (HCFS)

Hello, Regarding the Filesystem abstraction support, we are planning to use a distributed file system which complies with Hadoop Compatible File System (HCFS) standard in place of standard HDFS. According to the documentation

[jira] [Created] (FLINK-5811) Harden YarnClusterDescriptorTest

Till Rohrmann created FLINK-5811: Summary: Harden YarnClusterDescriptorTest Key: FLINK-5811 URL: https://issues.apache.org/jira/browse/FLINK-5811 Project: Flink Issue Type: Bug

RE: [DISCUSS] Table API / SQL indicators for event and processing time

Hi, My initial thought would be that it makes more sense to thave procTime() and rowTime() only as functions which in fact are to be used as markers. Having the value (even from special system attributes does not make sense in some scenario such as the ones for creating windows, e.g., If you

[jira] [Created] (FLINK-5807) improved wording for doc home page

David Anderson created FLINK-5807: - Summary: improved wording for doc home page Key: FLINK-5807 URL: https://issues.apache.org/jira/browse/FLINK-5807 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-5806) TaskExecutionState toString format have wrong key

shijinkui created FLINK-5806: Summary: TaskExecutionState toString format have wrong key Key: FLINK-5806 URL: https://issues.apache.org/jira/browse/FLINK-5806 Project: Flink Issue Type: Bug

Re: Handling skewness and Heterogeniety

Dear Fabian, Can you have a look into this issue. What actions will be required to resolve this one? https://issues.apache.org/jira/browse/FLINK-1725 Regards, Anis On Wed, Feb 15, 2017 at 6:36 PM, Fabian Hueske wrote: > Hi Anis, > > Flink uses regular hash-partitioning

[jira] [Created] (FLINK-5805) improve docs for ProcessFunction

David Anderson created FLINK-5805: - Summary: improve docs for ProcessFunction Key: FLINK-5805 URL: https://issues.apache.org/jira/browse/FLINK-5805 Project: Flink Issue Type: Improvement

Re: Handling skewness and Heterogeniety

Hi Anis, Flink uses regular hash-partitioning to shuffle records and does not have a mechanism to counter data skew (other than scaling out). Heterogeneous hardware can (to some extend) be addressed by adapting the number of processing slots (or task managers) per machine, i.e., configure fewer

Re: [DISCUSS] Table API / SQL indicators for event and processing time

Hi all, at first I also thought that built-in functions (rowtime() and proctime()) are the easiest solution. However, I think to be future-proof we should make them system attributes; esp. to relate them to a corresponding table in case of multiple tables. Logically they are attributes of