[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-755:
Status: Patch Available (was: Open)
> standardizing json values stored in ZK
>
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-755:
Attachment: kafka-755-v1.patch
This patch standardizes the reading and writing to zookeeper values a
David,
The API that you are looking for is OffsetRequest. If you pass in -2 as the
value for Time, it will get you the earliest offset available for that
partition. If you pass in -1, it will get you the latest offset.
You can find more information about the OffsetRequest and OffsetResponse
APIs
Is there currently a way to get the latest offset (or close to the
latest) for a partition? Is this covered by the Offset API, and if so
could someone explain this API a bit?
I'd like to write a consumer that can start from 0 (like unix cat) or
start from the most recent (like unix tail).
Th
Joe,
What is the JIRA for this issue ?
Thanks,
Neha
On Sun, Feb 17, 2013 at 4:14 PM, Joe Stein wrote:
> for #1 we should come up with some way for folks to deal with that as more
> will once released trying to build on 2.9.2 and have to work around
>
> maybe have the sbt build write something
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582795#comment-13582795
]
Neha Narkhede commented on KAFKA-755:
-
I updated the wiki with the proposed zookeeper p
Sriram Subramanian created KAFKA-767:
Summary: Message Size check should be done after assigning the
offsets
Key: KAFKA-767
URL: https://issues.apache.org/jira/browse/KAFKA-767
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian reassigned KAFKA-765:
Assignee: Sriram Subramanian
> Corrupted messages in produce request could shutd
[
https://issues.apache.org/jira/browse/KAFKA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582461#comment-13582461
]
Guozhang Wang commented on KAFKA-762:
-
Reviewed the patch, looks good to me.
Just one
Sriram Subramanian created KAFKA-766:
Summary: Isr shrink/expand check is fragile
Key: KAFKA-766
URL: https://issues.apache.org/jira/browse/KAFKA-766
Project: Kafka
Issue Type: Bug
Af
[
https://issues.apache.org/jira/browse/KAFKA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582415#comment-13582415
]
Guozhang Wang commented on KAFKA-763:
-
Just a quick question: what is an "unclean leade
[
https://issues.apache.org/jira/browse/KAFKA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582396#comment-13582396
]
Jun Rao commented on KAFKA-765:
---
One way to fix this is to only convert IOException from segm
Jun Rao created KAFKA-765:
-
Summary: Corrupted messages in produce request could shutdown the
broker
Key: KAFKA-765
URL: https://issues.apache.org/jira/browse/KAFKA-765
Project: Kafka
Issue Type: Bu
[
https://issues.apache.org/jira/browse/KAFKA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-208.
-
Resolution: Fixed
This is fixed in the new 0.8 protocol
https://cwiki.apache.org/confluence/display/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582351#comment-13582351
]
Colin B. commented on KAFKA-208:
Polling for many topics in one request seems to be handled
15 matches
Mail list logo