jcustenborder/flume-ng-rabbitmq — pull request #2 by kirkgray (2012-06-28 03:08:17+00:00)
Title: Updates to allow more flexible configuration.

Makes things a little easier/more flexible so you can declare a queue name OR an exchange name, and includes supporting code changes:

Summary:

1) Make the configuration read in RabbitMQUtil honor the exchange configuration
2) Make queue name configuration optional
3) Check for exchange name, and declare exchange, then check for queue name, and if not specified, grab dynamic queue name
4) Allow for configuration of topic keys
5) Add values to RabbitMQConstants
6) Updated README to address new config options
7) Require EITHER queue or exchange to be declared

Take a look and let me know what you think. It shouldn't have changed the way your base case worked.