Re: Want Flink startup issues :-)

2016-02-06 Thread Chiwan Park
Hi Dongwon, Yes, the things to do are picking an issue (by assigning the issue to you or commenting on the issue) and make changes and send a pull request for it. Welcome! :) Regards, Chiwan Park > On Feb 6, 2016, at 3:31 PM, Dongwon Kim wrote: > > Hi Fabian, Matthias, Robert! > > Thank you

Re: Want Flink startup issues :-)

2016-02-06 Thread Dongwon Kim
Hi Chiwan! That's what I wanted to know! Thanks! Dongwon Kim 2016-02-06 22:00 GMT+09:00 Chiwan Park : > Hi Dongwon, > > Yes, the things to do are picking an issue (by assigning the issue to you or > commenting on the issue) and make changes and send a pull request for it. > > Welcome! :) > > Re

Re: [ANNOUNCE] Please annotate public interfaces!

2016-02-06 Thread Stephan Ewen
Hi! These suggestions sound good in general. I am wondering if "Experimental" is not the wrong word here, because most of the things are not experimental, but just possibly subject to slight changes (though API breaking). Experimental has the connotation that something is unstable (execution wis

Re: [ANNOUNCE] Please annotate public interfaces!

2016-02-06 Thread Stephan Ewen
What "Experimental" is really saying is "Public, but not API stable". In that sense, "Internal" is not suitable, as it suggests that a method will never be public. What would you think of renaming "Experimental" to "PublicEvolving" ? That would carry pretty much explicitly the meaning that it is

[jira] [Created] (FLINK-3350) Increase timeouts on Travis Builds

2016-02-06 Thread Stephan Ewen (JIRA)
Stephan Ewen created FLINK-3350: --- Summary: Increase timeouts on Travis Builds Key: FLINK-3350 URL: https://issues.apache.org/jira/browse/FLINK-3350 Project: Flink Issue Type: Bug Comp

Re: [VOTE] Release Apache Flink 0.10.2 (RC1)

2016-02-06 Thread Stephan Ewen
+1 (binding) - Built the code (Linux x64, Scala 2.10, Hadoop 2.3.0) - Ran all tests - Checked that there are no cross-version dependencies - Checked that LICENSE and NOTICE are up to date - Check planVisualizer util - ran examples from command line - tested web frontend on Firefox an

[jira] [Created] (FLINK-3351) RocksDB Backend cannot determine correct local db path

2016-02-06 Thread Gyula Fora (JIRA)
Gyula Fora created FLINK-3351: - Summary: RocksDB Backend cannot determine correct local db path Key: FLINK-3351 URL: https://issues.apache.org/jira/browse/FLINK-3351 Project: Flink Issue Type: Bu

[jira] [Created] (FLINK-3352) RocksDB Backend cannot determine correct hdfs path

2016-02-06 Thread Gyula Fora (JIRA)
Gyula Fora created FLINK-3352: - Summary: RocksDB Backend cannot determine correct hdfs path Key: FLINK-3352 URL: https://issues.apache.org/jira/browse/FLINK-3352 Project: Flink Issue Type: Bug

Tips for testing

2016-02-06 Thread Stefano Baghino
Hi everybody, as I've recently started contributing to Flink, I'd like to ask you a few tips on how you normally run the tests to ensure that everything runs smoothly before pushing the code to CI. First, I'd like to point out two issues in particular I had: 1. some test suites (KMeansWithBro

[jira] [Created] (FLINK-3353) CSV-related tests may fail depending on locale

2016-02-06 Thread Stefano Baghino (JIRA)
Stefano Baghino created FLINK-3353: -- Summary: CSV-related tests may fail depending on locale Key: FLINK-3353 URL: https://issues.apache.org/jira/browse/FLINK-3353 Project: Flink Issue Type:

[jira] [Created] (FLINK-3354) RocksDB should compute checkpoint size based on backup file size

2016-02-06 Thread Gyula Fora (JIRA)
Gyula Fora created FLINK-3354: - Summary: RocksDB should compute checkpoint size based on backup file size Key: FLINK-3354 URL: https://issues.apache.org/jira/browse/FLINK-3354 Project: Flink Iss

[jira] [Created] (FLINK-3355) Allow passing RocksDB Option to RocksDBStateBackend

2016-02-06 Thread Gyula Fora (JIRA)
Gyula Fora created FLINK-3355: - Summary: Allow passing RocksDB Option to RocksDBStateBackend Key: FLINK-3355 URL: https://issues.apache.org/jira/browse/FLINK-3355 Project: Flink Issue Type: Impro

Re: [ANNOUNCE] Please annotate public interfaces!

2016-02-06 Thread Fabian Hueske
I agree, Experimental rather suggests unstable behavior than potentially changing interfaces. +1 for renaming to @PublicEvolving. Other opinions on strictly annotating all public interfaces with @Public / @PublicEvolving and defaulting to @Internal for all remaining interfaces? 2016-02-06 15:27 G