ll change, though, to allow a server-override
> parameter that would have the server either always compress the data or
> always decompress it before writing it to the log.
>
> -Jay
>
> On Thu, Jul 19, 2012 at 10:24 AM, Michal Hariš >wrote:
>
> > Does it mean tha
Does it mean that currently if a producer publishes an uncompressed message
to the server which has local log format configured to compressed,
consumers will receive compressed messages when fetching?
On Jul 19, 2012 5:08 PM, "Jay Kreps (JIRA)" wrote:
>
> [
> https://issues.apache.org/jira/b
I can confirm, it has bitten me few days ago, had it been documented I
wouldn't need to spend an hour looking into the scala code which serializes
the gzipped message only to find out theres another message inside when
writing a php client.
I also think it does actually complicate the matter becau
; wrote:
> Awesome, I built a RESTful Proxy last week so I will integrate your library
> and check that out. I'll publish my Proxy code soon, it is getting thrashed
> internally right now.
> On Jul 15, 2012 4:21 PM, "Michal Hariš" wrote:
>
> > Hi all,
&g
Hi all,
I have a long interest in pub-sub and have written several variants of
proxies/bridges to JMS ( ActiveMQ, HornetQ and some others) in Java and I
share the motivations behind Kafka project (esp. the idea of keeping the
consumption state at the consumer side really speaks to my heart and als
