Re: Jobmanager drops upon submitting a jar

2017-04-13 Thread amir bahmanyari
It ends up to be a release gap between the build env libs and the runtime.nothing else.Am updating everything to the latest+greatest.With the latest Flink, and the current (old) code the Maven reports:[ERROR]   symbol:   class FlinkKafkaConsumer08 Meaning it needs to be replaced with the latest

Re: Jobmanager drops upon submitting a jar

2017-04-13 Thread amir bahmanyari
Thanks so much for your help.Below is whats in JM logs.Appreciate your feedback. 2017-04-12 15:51:01,723 WARN  org.apache.hadoop.util.NativeCodeLoader                       - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable2017-04-12

[jira] [Created] (FLINK-6305) flink-ml tests are executed in all flink-fast-test profiles

2017-04-13 Thread Nico Kruber (JIRA)
Nico Kruber created FLINK-6305: -- Summary: flink-ml tests are executed in all flink-fast-test profiles Key: FLINK-6305 URL: https://issues.apache.org/jira/browse/FLINK-6305 Project: Flink Issue

RE: Sliding Window - Weird behaviour

2017-04-13 Thread Radu Tudoran
Hi, You need to implement your own timer. You do this when you create your window by assigning the timer. In your custom timer you would need to implement the desired logic in the onElement method. You can keep a counter that you increment for each element up to your desired number of elements

Re: Sliding Window - Weird behaviour

2017-04-13 Thread madhairsilence
Hi Xingcan Thanks for the answer. But up to my understanding countWindow(4,2) - Should wait for 4 elements (or window not more than 4 element) and once the window is ready, slide two items Now if I have to stopped asking why questions and worry about my current problem, how do I achieve this

Re: Sliding Window - Weird behaviour

2017-04-13 Thread Xingcan Cui
​Hi harish, I will not argue for the correctness of the result​s, but just tell you why this happens. The countWindow(2, 1) can be regarded as two separate processes: 1) maintain a window whose size *not exceeds* 2 and 2) trigger window evaluation every single record. Actually, in Flink the two

[jira] [Created] (FLINK-6304) Clear a lot of useless import

2017-04-13 Thread sunjincheng (JIRA)
sunjincheng created FLINK-6304: -- Summary: Clear a lot of useless import Key: FLINK-6304 URL: https://issues.apache.org/jira/browse/FLINK-6304 Project: Flink Issue Type: Improvement

Re: [VOTE] Release Apache Flink 1.2.1 (RC2)

2017-04-13 Thread Gyula Fóra
Hi, Unfortunately I cannot test run the rc as I am on vacation. But we have been running pretty much the same build (+1-2 commits) in production for some time now. +1 from me Gyula On Thu, Apr 13, 2017, 08:27 Andrew Psaltis wrote: > +1 -- checked out all code, built

[jira] [Created] (FLINK-6303) Documentation support build in docker on OSX

2017-04-13 Thread Tao Meng (JIRA)
Tao Meng created FLINK-6303: --- Summary: Documentation support build in docker on OSX Key: FLINK-6303 URL: https://issues.apache.org/jira/browse/FLINK-6303 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-6302) Documentation build error on ruby 2.4

2017-04-13 Thread Tao Meng (JIRA)
Tao Meng created FLINK-6302: --- Summary: Documentation build error on ruby 2.4 Key: FLINK-6302 URL: https://issues.apache.org/jira/browse/FLINK-6302 Project: Flink Issue Type: Bug

Sliding Window - Weird behaviour

2017-04-13 Thread madhairsilence
I have a datastream 1,2,3,4,5,6,7 I applied a sliding countWindow as inputStream.keyBy("num").countWindow(2,1) I expect an output as 1,2 2,3 3,4 But am getting an output as 1 1,2 2,3 3,4 Why does the data slide first and then accumulate the window size -- View this message in context:

Re: [VOTE] Release Apache Flink 1.2.1 (RC2)

2017-04-13 Thread Andrew Psaltis
+1 -- checked out all code, built with all tests, ran local cluster, deployed example streaming jobs On Thu, Apr 13, 2017 at 2:26 AM, Andrew Psaltis wrote: > Ted -- I did not see those errors. My environment is: > Apache Maven 3.3.9

Re: [VOTE] Release Apache Flink 1.2.1 (RC2)

2017-04-13 Thread Andrew Psaltis
Ted -- I did not see those errors. My environment is: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00) Maven home: /usr/local/Cellar/maven/3.3.9/libexec Java version: 1.8.0_121, vendor: Oracle Corporation Java home: