Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Plain View
Kafka >> mail # dev >> Re: [jira] [Updated] (KAFKA-187) Add Snappy Compression as a Codec and refactor CompressionUtil and option on startup to select what the default codec


Copy link to this message
-
Re: [jira] [Updated] (KAFKA-187) Add Snappy Compression as a Codec and refactor CompressionUtil and option on startup to select what the default codec
So with regard to the
KAFKA-187<https://issues.apache.org/jira/browse/KAFKA-187> what
is the stance going to be on supporting new compression methods?  Is it
expected that all clients 'must' & will support them?  If not, is there a
set of 'required' compression codecs?  Jun mentioned not wanting every
language to re-implement a thick client, but where is the line between
thick and thin?  It seems like there needs be a clear set of expectations
for what a client implements, regardless of language or platform, or maybe
I'm off in the weeds..
+
Chris Burroughs 2011-11-11, 19:22
+
Jeffrey Damick 2011-11-12, 19:24
+
Jay Kreps 2011-11-12, 21:05
+
Jeffrey Damick 2011-11-13, 18:58
+
Jun Rao 2011-11-14, 00:57
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