you can publish locally
./sbt "++2.9.2 publish-local"
and then call it
"org.apache.kafka" % "kafka_2.9.2" % "0.8.0-beta1"
I am still having the same unauthorized message from
repository.apache.orgwill try a few other things and follow-up on the
INFRA ticket I created
during the release https://
Thanks for cleaning up the site. Overall, it looks cleaner. A few comments:
1. implementation: This is mostly about the 0.7 implementation. So it
probably should be added under 0.7.
2. 0.8 quickstart: Step 3, when the text says list topic, the command is
actually create topic. Step 4, not sure if
LinkedIn uses the first method for cross DC mirroring. For the second
method, there are 2 main issues. (1) Kafka depends on the ZK service to be
always available. For a ZK cluster to be available, you need a majority of
ZK servers to be up. If you set up a ZK cluster spanning only 2 data
centers, a
If you use MirrorMaker to mirror the data from the primary cluster to the
backup cluster, currently the offsets are not preserved btw the two
clusters. In other words, the offsets for the same message in the two
clusters are not necessarily the same.
Thanks,
Jun
On Sat, Jun 29, 2013 at 10:56 AM
Commented on the jira.
Thanks,
Jun
On Sat, Jun 29, 2013 at 6:21 AM, Jason Rosenberg wrote:
> I added this scenario to KAFKA-955.
>
> I'm thinking that this scenario could be a problem for ack=0 in general
> (even without controlled shutdown). If we do an "uncontrolled" shutdown,
> it seems t
Kafka 0.8 works great. I am able to use CLI as well as write my own
producers/consumers!
Checking Zookeeper... and I see all the topics and partitions created
successfully for 0.8.
Kafka 0.7 does not work!
Why Kafka 0.7? I am using Kafka Spout from Storm which is made for Kafka
0.7.
First I jus
