Wouldn't it be helpful to throw an error or a warning if the user
tries to create a topic with an invalid name? Currently neither the
API nor the CLI tools inform you that you are naming a topic in a way
you shouldn't.
And as Otis pointed out elsewhere in this thread this ties back into
the
If Storm 0.9.2. uses the SimpleConsumer, this could be a bug in the leader
fault tolerance logic in Storm itself. The high level consumer
(ZookeeperConsumerConnector) handles this automatically for you.
On Thu, Sep 4, 2014 at 8:31 AM, Guozhang Wang wangg...@gmail.com wrote:
Hi Siddharth,
The
Theo,
Wondering if changing those settings as suggested worked for you?
Thanks,
Neha
On Wed, Sep 3, 2014 at 12:51 AM, Theo Hultberg t...@iconara.net wrote:
that makes sense. if the size of each fetch is small then compression won't
do much, and that could very well explain the increase in
Actually, we do give you an error if an invalid topic is created through
CLI. When we add a create topic api, we can return the correct error code
too.
bin/kafka-topics.sh --zookeeper localhost:2181 --create --topic=te+dd
--partitions 1 --replication-factor 1
Error while executing topic command
This is great. Thanks for sharing! Does kafkat automatically figure out the
right reassignment strategy based on even data distribution?
On Wed, Sep 3, 2014 at 12:12 AM, Alexis Midon
alexis.mi...@airbedandbreakfast.com wrote:
Hi Marcin,
A few weeks ago, I did an upgrade to 0.8.1.1 and then
Filed https://issues.apache.org/jira/browse/KAFKA-1634 to track the change
and marked it for 0.8.2.
On Sun, Aug 31, 2014 at 5:20 PM, Dana Powers dana.pow...@rd.io wrote:
following up on this -- I think the online API docs for OffsetCommitRequest
still incorrectly refer to client-side
Guozhang,
It is probably best to create a child page for the main wiki and copy the
content from the LinkedIn wiki over to that. This way we can let other
people contribute to the wiki easily. Please modify the main wiki to point
to the new child page once this is done. Thanks for your help here!
head() is a scala method. Calling it from java requires you to figure out
the exact class name in byte code. A simpler way is to use the java
iterable api in KafkaStream. By default, it blocks on the hasNext()
call when there is no message.
Thanks,
Jun
On Sat, Sep 13, 2014 at 1:01 AM, Aarti
