Confusing "nil" value for topology.eventlogger.executors

[S G <sg...@gmail.com>]

Hi,

I see the value "nil" for topology.eventlogger.executors at
http://storm.apache.org/releases/1.0.0/Eventlogging.html

While other values are 0 or 1, "nil" seems really confusing especially
because it does not disable something, rather it enables something.
Something not expected of "nil" as per the word semantics. (IMHO)

How about creating an enum for this option, with values as follows?
NO_EVENT_LOGGING
ONE_ EL_PER_TOPOLOGY
ONE_EL_PER_WORKER

Benefit of this approach is that users dont need to rush to docs to see
what the values 0, 1 or "nil" means.

Thanks
SG