Allow output plugins to declare that, for a given configuration, workers are
not supported. Such reasons could include inability to share a resource
(like a listening socket, etc). This declaration will force a
single-worker setting and allow logstash to warn the user instead of
aborting.
Try to fix any @timestamp values if someone mucks with that field value
and turns it into a string through the json filter.
purge old and long-since-deprecated amqp plugins
- Include a (hopefully) better warning message when using an output
plugin that doesn't support workers.
- Remove worker_setup_skip hackery; not needed.
- update file and zeromq workers_not_supported settings
Be more obvious that worker count is ignored but otherwise work will continue
tcp in server mode doesn't support workers.
Merge pull request #732 from logstash/output-workers-not-supported

Allow output plugins to declare that, for a given configuration, workers...
Merge pull request #734 from logstash/purge-amqp-plugin

purge old and long-since-deprecated amqp plugins
- add test case
Merge pull request #733 from logstash/support-@timestamp-in-json-filter-better

Try to fix any @timestamp values if someone mucks with that field value
Merge git://github.com/logstash/logstash