+1
- Checked LICENSE and NOTICE files
- Read the readme.md
- Checked signature and checksums
- Built from sources
- Tested all examples in cluster mode
- Tested all examples in yarn mode
- Tested single yarn session per job
- Tested web-client job submission
- Tested WordCount with HDFS input
- Te
Gabor Gevay created FLINK-2255:
--
Summary: In the TopSpeedWindowing examples, every window contains
only 1 element, because event time is in millisec, but eviction is in sec
Key: FLINK-2255
URL: https://issues.apache.
I like moving the type system classes to core.
But one blocker so far was that the TupleX classes are in flink-java, and
no one moved them.
We have this long discussion pending whether we want to merge flink-core
and flink-java, actually...
On Sun, Jun 21, 2015 at 12:29 AM, Chiwan Park wrote:
Andra Lungu created FLINK-2254:
--
Summary: Add Bipartite Graph Support for Gelly
Key: FLINK-2254
URL: https://issues.apache.org/jira/browse/FLINK-2254
Project: Flink
Issue Type: New Feature
+1 for moving the whole type extractor and type information classes to
"flink-core".
The user cannot see "flink-core” because it is a hidden package from user’s
perspective.
So the package could be deployed with Scala version variation safely. I think
that we can
mix “flink-core” and some Scala