Home | About | Sematext search-lucene.com search-hadoop.com search-devops.com
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 Threaded View
Kafka >> mail # user >> why was auto.offset.reset default changed (so late in the game)?


Copy link to this message
-
Re: why was auto.offset.reset default changed (so late in the game)?
Jason,

If we default to smallest and a consumer doesn't override this, when it
migrates to 0.8, it will likely reconsume a lot of data. Quite of few
consumers are real time since they feed data to systems like Storm.

What do you think is the best way to communicate such config changes in the
future? It's discussed in the jira a bit. We can send it to the user
mailing list. However, I am not sure if everyone is paying attention to all
the emails.

Thanks

Jun

On Tue, Jun 18, 2013 at 1:28 PM, Jason Rosenberg <[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