…11 (Latest Release)

Storm is using a snakeyaml version that is now two revisions old. I have recently come across a dependency conflict when using Storm with JRuby 1.7.3. When running in ruby 1.9 mode JRuby utilizes the snakeyaml library, however the internal JRuby  version of snakeyaml 1.11. Since Storm is running an outdated version, it would make sense to propose the change in hopes of resolving this dependency conflict.

Enable java HashMap used for ZMQ messaging configuration

Details:
* For every Config there is a schema of type Object named with the
  _SCHEMA suffix (e.g., TOPOLOGY_WORKERS_SCHEMA)
* For simple Classes (String, Number, Boolean), just the Class is
  sufficient for the schema's value
* For other Classes, instances of the FieldValidator interface are used.
* FieldValidator declares a method to validate the field and a method to
  return a plain-language description of the criteria for the user.

Status: Compiles, but not tested.  Nothing makes use of the schemas yet.

…e topology

merge changes from nathanmarz/storm master

1. viewing log file
2. get/set log4j log level online

Fix for port allocation errors during tests

Launch workers with id and port properties

…curtu-millis-ticks

…use-543

build_release.sh  modified to avoid duplicated storm-core.jar files

…emove 'log' from port display

Add `drpc.childopts` config

Update project.clj - Bump snakeyaml dependency version from 1.9 to 1.11 (Latest Release)

…o lyogavin-default_ackers1

Other cosmetic changes.

Conflicts:
	conf/defaults.yaml
	storm-core/src/jvm/backtype/storm/Config.java

make FixedBatchSpout batch aware.

…eptions

Includes key in invalid config exception message

The topology.metrics.consumer.register is a list of hashes, but its schema was StringsValidator. Added a 'MapsValidator' (list of Map) and fixed the schema.

* Added a LoggingMetricsConsumer example of a MetricsConsumer. Use it by adding 'conf.registerMetricsConsumer(LoggingMetricsConsumer.class);' when you construct your topology.
* Added a dedicated appender to the example logback/cluster.xml called METRICS.
  Its log format omits the class and priority since with the dedicated appender those are redu

Specify jvm_opts when calling storm jar

Throw Exception if OpaqueValue's txId is ahead of batchTxId

LoggingMetricsConsumer, to dump metrics to log file

fix topology.metrics.consumer.register validation: Map, not String