If I don't provide an explicit key serializer but a serializer class (for value encoding), and then use a key in KeyedMessage, what will be the encoder used for key? Is it going to default to the same encoder used for value or the DefaultEncoder?
Thanks for the reply. But, when I did some more research, it seems like its using the same encoder for both. For example, if I provide serializer.class explicitly, this serializer is used for both key and value. However, if I don't specify any serializer, then it appears that Kafka defaults to DefaultEncoder. Is that what you ment?
Thanks again!! Soby Chacko On Wed, Apr 10, 2013 at 1:59 PM, Neha Narkhede <[EMAIL PROTECTED]>wrote:
This patch does the following: 1. Change Encoder and Decoder to map between object and byte rather than between Message and object. 2. Require two encoders for the producer and two decoders for the consumer. This follows the same pattern as before: in the producer there is now serializer.class and key.serializer.class. *By default key.serializer takes the same value as serializer.class*. If no key is specified then this parameter is essentially ignored. In the consumer ConsumerConnector now requires two decoders, one for the key and one for the value. So, if this is true, then doesn't that mean key.serializer gets default to whatever value serializer.class takes, not the DefaultEncoder?
Thanks again, Soby Chacko
On Fri, Apr 12, 2013 at 11:38 AM, Neha Narkhede <[EMAIL PROTECTED]>wrote:
Correct, I should've been more specific. "key.serializer.class" defaults to whatever "serializer.class" is set to.
On Fri, Apr 12, 2013 at 9:12 AM, Soby Chacko <[EMAIL PROTECTED]> wrote:
Neha Narkhede 2013-04-12, 16:21
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext