In this case, does the consumer code need to change, account for the
compression (or is this handled automatically in the consumer apis?).

If we decide to start compressing messages to a topic, can a consumer
seamlessly move between the transition from uncompressed to compressed?

On Tue, Jun 4, 2013 at 11:16 PM, Vadim Keylis <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB