Thanks Jun,
I completely missed your earlier reply in this thread. Changing to use the
javaapi makes the process a lot cleaner.
Thanks,
Chris
On Mon, Dec 3, 2012 at 11:26 AM, Jun Rao wrote:
> kafka.javaapi.consumer.SimpleConsumer has an api to get the topic metadata.
>
> Thanks,
>
> Jun
>
>
There is no reason the ClientUtils.fetchTopicMetadata should take broker
instances, that is totally unusable. I have a patch for this included in
KAFKA-642.
-Jay
On Mon, Dec 3, 2012 at 7:53 AM, Chris Curtin wrote:
> Hi,
>
> I was able to implement my own lookup code but have a few concerns abo
kafka.javaapi.consumer.SimpleConsumer has an api to get the topic metadata.
Thanks,
Jun
On Mon, Dec 3, 2012 at 7:53 AM, Chris Curtin wrote:
> Hi,
>
> I was able to implement my own lookup code but have a few concerns about
> this long term:
> - the Broker class is marked as 'private' in the Sc
Hi,
I was able to implement my own lookup code but have a few concerns about
this long term:
- the Broker class is marked as 'private' in the Scala code. IntelliJ gives
me an error about using it, but the runtime lets me use it and get the
host/port out.
- I have to know a lot about the structure
The clientid is used to identify a particular client application. This
is used by the server side request logging to identify the client
sending a particular request. The clientid is also used to give
meaningful names to the mbeans for producer/consumer clients.
Also, there are 2 ways to send the
The offset now begins at 0 and increases sequentially for each partition.
The offset is identical across all replicas of that partition on different
brokers, but amongst different partitions the offsets are independent (as
before). The offset of a committed message is unique within that
topic/parti
To use SimpleConsumer, you need to send TopicMetadataRequest (available in
SimpleConsumer) to figure out the leader of each partition before making
the fetch requests.
In both 0.7 and 0.8, a fetch request fetches data starting at the provided
offset. In 0.8, offset is a sequential and evergrowing
Hi,
First, thanks for 0.8.0 I'm really impressed with the redundancy
and simplification of the producer and consumer models.
I've upgraded my consumers from 0.7.2 to 0.8.0 and have some questions.
I am using the Simple Consumer since I need to support replay of messages
at request from the clien
