The Flink-On-Tez tests are failing frequently due to deadlocks in Tez 0.6.1.

Since this is outside of the scope of Flink and Flink-On-Tez is not a core
feature of Flink, it is OK to ignore these tests until a new Tez version is
released, which we can try.

https://s3.amazonaws.com/archive.travis-ci.org/jobs/67848150/log.txt

- fail on command error / unset variable
- make Mac OS X compatible
- fix uberjar file limit detection
- remove obsolete yarn part
- cleanup

This closes #811.

This closes #850.

This closes #790.

This closes #842.

This closes #849, #850.

This PR adds an iterator.hasNext() check in the groupReduceOnNeighbors method, fixing the NoSuchElementException bug reported in FLINK-2178.

@vasia , @StephanEwen, maybe we can merge this before the upcoming 0.9 release :)
Thanks!

Author: andralungu <lungu.andra@gmail.com>

Closes #799 from andralungu/groupReduceOnBug and squashes the following commits:

0a09e85 [andralungu] [FLINK-2178][gelly] Fixed groupReduceOnNeighbors bug

Similar to the vertex-centric approach, this PR enables users to access the total number of vertices from within the gather, sum and/or apply functions of a GSA iteration.

Author: andralungu <lungu.andra@gmail.com>

Closes #779 from andralungu/numVerticesGSA and squashes the following commits:

cffd944 [andralungu] [FLINK-2140][gelly] Allowed access to the number of vertices in the GSA functions

SumAggregator and ComparableAggregator had some code duplication for
accessing the specified field for different kinds of types (Tuple, Pojo,
Array, simple).

This PR simplifies Gelly's Jaccard example by using the more efficient reduceOnNeighbors rather than groupReduceOnNeighbors.

Author: andralungu <lungu.andra@gmail.com>

Closes #770 from andralungu/jaccardImprovement and squashes the following commits:

6e77f8d [andralungu] [FLINK-2149][gelly] Simplified Jaccard Example

Closes #851

To make tests more stable as a temporal fix
additional bug fix: isRunning was not volatile in AbstractStormSpoutWrapper

Closes #845

This closes #837.

This closes #830.

[FLINK-2225] [scheduler] Excludes static code paths from co-location constraint to avoid scheduling problems

This closes #843.

Failing jobs executed in the YARN cluster mode leave the application
container in the "SUCCEEDED" final state. While for long-running Flink
YARN clusters where multiple jobs are run, this is fine, for single jobs
it is appropriate to mark the application as failed.

This closes #838.

This closes #840.

Closes #835

This is just a clear documentation of the problem for the 0.9 release.

Closes #839

This closes #841.

- Pressing the state button in the job history view (like SCHEDULED, FINISHED)
  sends a "null" (String) as group vertex ID, which results in an
  IllegalArgumentException. Fixed by check and early return.

- The JM log is flooded by INFO-level messages when no GlobalJobParameters are
  set (common case). Fixed by decreasing the log level of these message to
  DEBUG.

[storm-compat] Moved Storm-compatibility to flink-contrib and split flink-contrib into small sub-projects

Closes #573

  - re-introduced possibility to specify output type for addSource()
  - split StormCollector into Abstract-, Bolt-, and Spout-Collector
additional minor changes:
  - removed unnecessary "unused" tags
  - fixed comment typos
  - added missing license header in SingleJoin example files