The new implementation separates the various concerns formerly mixed up in the
example code.  Also, we are now using tick tuples (introduced in Storm 0.8)
instead of spawning manual threads for carrying out periodical tasks.

Lastly, we add 192 unit tests for the new implementation that brings the test
coverage for the Rolling Count from 0% to almost 100%.

Note: Adding those unit tests required changes to the build (m2-pom.xml),
notably new test dependencies and moving the existing Java code from src/jvm/*
to src/jvm/main/*.  The latter was required so that the test runner triggered
by Maven can tell code (src/jvm/main) and tests (src/jvm/test) apart.

Complete refactoring of the Rolling Count example

SlidingWindowCounterTest: add missing @test annotation to unit test

Yes, we iterate through the list twice, but we no longer have
a function that does two things.

This commit is best explained by describing the behavior of
RollingTopWords in its absence.

Let's say the word "Bieber" appears in the tweet stream at a very high
rate for half an hour, and then is *never heard again*.

This will insert the word "Bieber" into our rankings object downstream.

Note that there is nothing to *remove* the word "Bieber" from the
rankings object downstream. Let us assume that, during its half-hour,
the word "Bieber" appears *more than five times as often* as other
highly-ranked words. Then the very *last* "Bieber" report (in which
"Bieber" has only appeared for the first minute of the five-minute
window) will still be able to hold a place in the rankings. Objects are
only lowered in the rankings by being outranked, or by *appearing again*
with a lower score.

*With* this change, we wipe zeros, and *then* wipe a slot. This means
that when we wipe the slot containing the last Bieber mentions, we
don't at that moment remove "Bieber" from our map. The *next* report
will include "Bieber" with a score of zero, removing "Bieber" from the
ranking object downstream.

added kafkaspout lag to transactionaltridentkafkaspout

Ensure zeros get reported.

update to storm 0.8.2

…artitions is ever called

fix unit tests to match new behavior

* split broker hosts into separate classes
* added test topology

* refactored partition handling

* moved to maven

* extracted emitter code to single class
* downgraded curator version to avoid conflicts

* removed unused leiningen project file

* updated pom and build instructions

…leException errors

Most of the original pull request (dated two years ago) was added to the
README.

See nathanmarz/storm-starter#3 for the original
pull request.

… is more silent on the logging side

…eceived

This fixes a ConcurrentModificationException that could be triggered when
using log4j to log Rankings#toString() from within a bolt's execute()
method.  Apparently a separate thread is used by log4j to perform the
logging, whose execution path could interweave with the bolt's own
thread.

Even though this is not necessarily a deficiency of the Rankings class
(which does not claim to be thread-safe), we still decided to make
Rankings#updateWith() thread-safe so that users do not run into errors
when using log4j & Co. for logging purposes.  In other words, we decided
to add this fix for the convenience of our users.

…eaner code

properly match Java package names and directory names for test classes

…ialiser being used. Moved multilang classes to multilang directory.

…es. Updated dependencies.

…d Immission to ShellMsg and BoltMsg respectively. Documented ISerializer interface.

…d Immission to ShellMsg and BoltMsg respectively. Documented ISerializer interface.

… name.

…t.clj, update README

Align storm-starter with upstream Storm 0.9.0 (release).

…mit 8012cd7)