+1 on comparison with existing solutions. On a high level, it seems nice to
have a transform library inside Kafka.. a lot of the building blocks are
already there to build a stream processing framework. However the details
are tricky to get right I think this discussion will get a lot more
Hi,
I'm looking forward to a benchmark which can explain how many total number
of topics and partitions can be created in a cluster of n nodes, given the
message size varies between x and y bytes and how does it vary with varying
heap sizes and how it affects the system performance.
e.g. the
Gwen,
We have a compilation of notes from comparison with other systems. They
might be missing details that folks who worked on that system might be able
to point out. We can share that and discuss further on the KIP call.
We do hope to include a DSL since that is the most natural way of
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33620/#review93110
---
I did an initial pass over the code (excluding tests) and left some
Hi Folks,
I would like to understand the best practices when using kafka as the
source-of-truth, given the fact that I want to pump in data to Kafka using
http methods.
What are the current production configurations for such a use case:-
1. Kafka-http-client - is it scalable the way Nginx is ??
On July 27, 2015, 1:32 p.m., Ismael Juma wrote:
core/src/main/scala/kafka/api/FetchResponse.scala, line 82
https://reviews.apache.org/r/33620/diff/13/?file=1021998#file1021998line82
Casts are to be avoided in Scala, pattern matching is a better way to
do this:
[
https://issues.apache.org/jira/browse/KAFKA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642865#comment-14642865
]
Sriharsha Chintalapani commented on KAFKA-1682:
---
[~ijuma] Here it is
[
https://issues.apache.org/jira/browse/KAFKA-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-2162:
--
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-1682
Kafka Auditing
[
https://issues.apache.org/jira/browse/KAFKA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642850#comment-14642850
]
Ismael Juma commented on KAFKA-1682:
One of the in-scope items in the wiki page is
[
https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-1686 started by Sriharsha Chintalapani.
-
Implement SASL/Kerberos
---
On July 27, 2015, 1:32 p.m., Ismael Juma wrote:
core/src/main/scala/kafka/api/FetchResponse.scala, line 82
https://reviews.apache.org/r/33620/diff/13/?file=1021998#file1021998line82
Casts are to be avoided in Scala, pattern matching is a better way to
do this:
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642821#comment-14642821
]
Rajasekar Elango commented on KAFKA-1690:
-
[~harsha_ch] Is there any documentation
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642829#comment-14642829
]
Sriharsha Chintalapani commented on KAFKA-1690:
---
[~erajasekar] I am putting
[
https://issues.apache.org/jira/browse/KAFKA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642868#comment-14642868
]
Ismael Juma commented on KAFKA-1682:
[~harsha_ch], thanks for the link and for making
Hey Yi,
Great points. I think for some of this the most useful thing would be to
get a wip prototype out that we could discuss concretely. I think Yasuhiro
and Guozhang took that prototype I had done, and had some improvements.
Give us a bit to get that into understandable shape so we can
[
https://issues.apache.org/jira/browse/KAFKA-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643016#comment-14643016
]
Gwen Shapira commented on KAFKA-2365:
-
BTW. Two connectors that appeared in the KIP
[
https://issues.apache.org/jira/browse/KAFKA-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-2321:
-
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/KAFKA-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643107#comment-14643107
]
ASF GitHub Bot commented on KAFKA-2321:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/KAFKA-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643129#comment-14643129
]
Guozhang Wang commented on KAFKA-2349:
--
Committed to the repo, thanks!
[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2367:
-
Summary: Add Copycat runtime data API (was: Add Copycat runtime API)
Add
I think there is still a subtle difference between async with acks = 0
and async with callback, that when the #.max-inflight-requests has
reached the subsequent requests cannot be sent until previous responses are
returned (which could happen, for example, when the broker is slow /
network issue
[
https://issues.apache.org/jira/browse/KAFKA-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2368:
-
Component/s: copycat
Add Copycat standalone CLI
--
[
https://issues.apache.org/jira/browse/KAFKA-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2366:
-
Component/s: copycat
Initial patch for Copycat
-
[
https://issues.apache.org/jira/browse/KAFKA-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2376:
-
Component/s: copycat
Add Copycat metrics
---
[
https://issues.apache.org/jira/browse/KAFKA-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2373:
-
Component/s: copycat
Copycat distributed offset storage
So basically this means that with acks = 0, their is no guarantee that the
message has been received by Kafka broker. I am just wondering, why would
anyone be using acks = 0, since anyone using kafka and doing
producer.send() would want that, their message got to kafka brokers. Also
as Jay said,
Yeah, using acks=0 should result in higher throughput since we are not
limited by the roundtrip time to the broker.
Btw. regarding in-flight requests: With acks = 1 (or -1), can we send
a message batch to a partition before the brokers acked a previous
request? Doesn't it risk getting messages
[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-2350:
---
Description:
There are some use cases in stream processing where it is helpful to be able to
[
https://issues.apache.org/jira/browse/KAFKA-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643087#comment-14643087
]
Neha Narkhede commented on KAFKA-2365:
--
Worth discussing a process for including a
[
https://issues.apache.org/jira/browse/KAFKA-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-2349:
-
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/KAFKA-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643014#comment-14643014
]
Gwen Shapira commented on KAFKA-2365:
-
I added a component, added you as component
[
https://issues.apache.org/jira/browse/KAFKA-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2371:
-
Component/s: copycat
Add distributed coordinator implementation for Copycat
[
https://issues.apache.org/jira/browse/KAFKA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2375:
-
Component/s: copycat
Implement elasticsearch Copycat sink connector
[
https://issues.apache.org/jira/browse/KAFKA-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2369:
-
Component/s: copycat
Add Copycat REST API
[
https://issues.apache.org/jira/browse/KAFKA-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2374:
-
Component/s: copycat
Implement Copycat log/file connector
[
https://issues.apache.org/jira/browse/KAFKA-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2370:
-
Component/s: copycat
Add pause/unpause connector support
[
https://issues.apache.org/jira/browse/KAFKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2379:
-
Component/s: copycat
Add Copycat documentation
-
[
https://issues.apache.org/jira/browse/KAFKA-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2378:
-
Component/s: copycat
Add Copycat embedded API
[
https://issues.apache.org/jira/browse/KAFKA-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2377:
-
Component/s: copycat
Add copycat system tests
[
https://issues.apache.org/jira/browse/KAFKA-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2372:
-
Component/s: copycat
Copycat distributed config storage
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/97
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/KAFKA-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2365:
-
Component/s: copycat
Copycat checklist
-
Key:
[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2367:
-
Component/s: copycat
Add Copycat runtime data API
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643065#comment-14643065
]
Mayuresh Gharat commented on KAFKA-2260:
I think, when 2 producers are trying to
Hi Prabhjot,
Confluent has a REST proxy with docs that may give some guidance:
http://docs.confluent.io/1.0/kafka-rest/docs/intro.html The new producer
that it uses is very efficient, so you should be able to get pretty good
throughput. You take a bit of a hit due to the overhead of sending data
If only we had some sort of system test framework with a producer
performance test that we could parameterize with the different acks
settings to validate these performance differences...
wrt out of order: yes, with 1 in flight requests with retries, messages
can get out of order. Becket had a
[
https://issues.apache.org/jira/browse/KAFKA-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643136#comment-14643136
]
Alexander Demidko commented on KAFKA-2303:
--
I think in our case we had too many
If you are used to map-reduce patterns, this sounds like a perfectly
natural way to process streams of data.
Call the first consumer map-combine-log, the topic shuffle-log and
the second consumer reduce-log :)
I like that a lot. It works well for either embarrassingly parallel
cases, or so much
See https://builds.apache.org/job/KafkaPreCommit/164/changes
[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643249#comment-14643249
]
Guozhang Wang commented on KAFKA-2350:
--
[~becket_qin], I was not considering the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33620/#review93177
---
On July 24, 2015, 4:13 p.m., Jun Rao wrote:
core/src/main/scala/kafka/network/SocketServer.scala, line 264
https://reviews.apache.org/r/36652/diff/3/?file=1020607#file1020607line264
Not sure if it's better to keep the thread alive on any throwable. For
unexpected exceptions, it
[
https://issues.apache.org/jira/browse/KAFKA-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643179#comment-14643179
]
Ismael Juma commented on KAFKA-2364:
Coincidentally a CONTRIBUTING.md was added today
For a little background, the difference between this partitioner and the
default one is that it breaks the deterministic mapping from key to
partition. Instead, messages for a given key can end up in either of two
partitions. This means that the consumer generally won't see all messages
for a
adding the open source alias. This email started off as a broader
discussion around the new consumer. I was zooming into only the aspect of
poll() being the only mechanism for driving the heartbeats.
Yes the lag is the effect of the problem (not the problem). Monitoring the
lag is important as
[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643442#comment-14643442
]
Jason Gustafson commented on KAFKA-2350:
[~becket_qin] I think that we're on the
I think if we recommend a longer session timeout, then we should expose the
heartbeat frequency in configuration since this generally controls how long
normal rebalances will take. I think it's currently hard-coded to 3
heartbeats per session timeout. It could also be nice to have an explicit
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36858/
---
Review request for kafka.
Bugs: KAFKA-2120
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643399#comment-14643399
]
Mayuresh Gharat commented on KAFKA-2120:
Created reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Gharat updated KAFKA-2120:
---
Status: Patch Available (was: Open)
Add a request timeout to NetworkClient
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Gharat updated KAFKA-2120:
---
Attachment: KAFKA-2120.patch
Add a request timeout to NetworkClient
Hey Kartik,
Totally agree we don't want people tuning timeouts in the common case.
However there are two ways to avoid this:
1. Default the timeout high
2. Put the heartbeat in a separate thread
When we were doing the consumer design we discussed this tradeoff and I
think the conclusion we came
Gwen - this is really like two steps of map reduce though, right? The first
step does the partial shuffle to two partitions per key, second step does
partial reduce + final full shuffle, final step does the final reduce.
This strikes me as similar to partition assignment strategies in the
[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643349#comment-14643349
]
Jason Gustafson commented on KAFKA-2350:
There's one interesting implementation
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36858/
---
(Updated July 27, 2015, 9:09 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643418#comment-14643418
]
Jiangjie Qin commented on KAFKA-2350:
-
[~hachikuji], I am with [~guozhang] that it is
Kartik, on your second point about timeouts with poll() and heartbeats, the
consumer now handles this properly. KAFKA-2123 introduced a
DelayedTaskQueue and that is used internally to handle processing events at
the right time even if poll() is called with a large timeout. The same
mechanism is
[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643418#comment-14643418
]
Jiangjie Qin edited comment on KAFKA-2350 at 7/27/15 9:45 PM:
--
This is due to the zookeeper path storing the previous owner info hasn't
been deleted at the moment. If the rebalance completes after retry, it
should be fine.
Jiangjie (Becket) Qin
On Fri, Jul 24, 2015 at 6:54 PM, Kris K squareksc...@gmail.com wrote:
Hi,
I started seeing these errors in the
[
https://issues.apache.org/jira/browse/KAFKA-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643573#comment-14643573
]
Xuan Gong commented on KAFKA-2268:
--
Looks like this is duplicate with
[
https://issues.apache.org/jira/browse/KAFKA-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643625#comment-14643625
]
Xuan Gong commented on KAFKA-2130:
--
move
{code}
stream.close();
{code}
to the finally
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643532#comment-14643532
]
Sourabh Chandak commented on KAFKA-1690:
[~sriharsha] Will this patch unblock the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36858/
---
(Updated July 27, 2015, 10:31 p.m.)
Review request for kafka.
Bugs:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36858/#review93189
---
Looks pretty good overall. Found mostly trivial stuff.
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643597#comment-14643597
]
Sriharsha Chintalapani commented on KAFKA-1690:
---
[~sourabh0612] Yes. It
@Ewen, good point about batching. Yes, it would be tricky if we want to do
a per-key conditional produce. My understanding is that the prerequisite of
this KIP is:
1. Single producer for each partition.
2. Acks=-1, max.in.flight.request.per.connection=1, retries=SOME_BIG_NUMBER
The major problem
I guess it depends on whether the original producer did any map
tasks or simply wrote raw data. We usually advocate writing raw data,
and since we need to write it anyway, the partitioner doesn't
introduce any extra hops.
Its definitely useful to look at use-cases and I need to think a bit
more
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643533#comment-14643533
]
Mayuresh Gharat commented on KAFKA-2120:
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Gharat updated KAFKA-2120:
---
Attachment: KAFKA-2120_2015-07-27_15:31:19.patch
Add a request timeout to NetworkClient
Try bouncing the host that appears in the stored data section.
Thanks,
Mayuresh
On Mon, Jul 27, 2015 at 3:41 PM, Jiangjie Qin j...@linkedin.com.invalid
wrote:
This is due to the zookeeper path storing the previous owner info hasn't
been deleted at the moment. If the rebalance completes after
Ashish K Singh created KAFKA-2381:
-
Summary: Possible ConcurrentModificationException while
unsubscribing from a topic in new consumer
Key: KAFKA-2381
URL: https://issues.apache.org/jira/browse/KAFKA-2381
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643703#comment-14643703
]
Ashish K Singh commented on KAFKA-2381:
---
[~gwenshap] could you take a look when you
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-2381:
--
Attachment: KAFKA-2381_2015-07-27_17:56:00.patch
Possible ConcurrentModificationException
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643699#comment-14643699
]
Ashish K Singh commented on KAFKA-2381:
---
Updated reviewboard
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36871/#review93215
---
core/src/test/scala/integration/kafka/api/ConsumerTest.scala (line
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-2381:
--
Status: Patch Available (was: Open)
Possible ConcurrentModificationException while
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-2381:
--
Attachment: KAFKA-2381.patch
Possible ConcurrentModificationException while unsubscribing from
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36871/
---
Review request for kafka.
Bugs: KAFKA-2381
[
https://issues.apache.org/jira/browse/KAFKA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643716#comment-14643716
]
Ashish K Singh commented on KAFKA-313:
--
[~gwenshap] need help with getting this KIP to
[
https://issues.apache.org/jira/browse/KAFKA-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Wang updated KAFKA-2360:
---
Description:
Run kafka-consumer-perf-test.sh --help to show help information, but found 3
parameters
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643658#comment-14643658
]
Sourabh Chandak commented on KAFKA-1690:
Awesome!
When will this be integrated to
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36871/
---
(Updated July 28, 2015, 12:56 a.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643693#comment-14643693
]
Ashish K Singh commented on KAFKA-2381:
---
Created reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643710#comment-14643710
]
Ashish K Singh commented on KAFKA-2275:
---
[~guozhang] I think this is in good shape
[
https://issues.apache.org/jira/browse/KAFKA-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643714#comment-14643714
]
Ashish K Singh commented on KAFKA-2301:
---
[~junrao], [~gwenshap] can any of you help
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36871/#review93213
---
Ouch. Hard to believe this wasn't caught yet.
[
https://issues.apache.org/jira/browse/KAFKA-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Wang updated KAFKA-2360:
---
Description:
Run kafka-consumer-perf-test.sh --help to show help information, but found 3
parameters
Stevo Slavic created KAFKA-2380:
---
Summary: Publish Kafka snapshot Maven artifacts
Key: KAFKA-2380
URL: https://issues.apache.org/jira/browse/KAFKA-2380
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643843#comment-14643843
]
Ashish K Singh commented on KAFKA-2381:
---
Updated reviewboard
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36871/
---
(Updated July 28, 2015, 4:56 a.m.)
Review request for kafka.
Bugs:
1 - 100 of 131 matches
Mail list logo
