[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698296#comment-14698296
]
Martin Kleppmann commented on KAFKA-2367:
-
Just looked at this in the contex
I'm with Sriram -- Kafka is all about streams already (or topics, to be
precise, but we're calling it "stream processing" not "topic processing"), so I
find "Kafka Streams", "KStream" and "Kafka Streaming" all confusing, since they
seem to imply that other bits of Kafka are not about streams.
I
Martin Kleppmann created KAFKA-1308:
---
Summary: Publish jar of test utilities to Maven
Key: KAFKA-1308
URL: https://issues.apache.org/jira/browse/KAFKA-1308
Project: Kafka
Issue Type: Wish
+1 for using exit status in the command-line tools. The other day I wanted to
modify a shell script to create a Kafka topic, using bin/kafka-topics.sh
--create --topic ...
The tool's behaviour is not very conducive to automation:
- If the topic creation was successful, it prints out a message a
+1. Verified all checksums and GPG signatures. Ran unit tests on source
package. Tested each of the binary packages by running Samza's hello-samza test
project on it, and verifying that it works.
There is a spurious zero-length file in that directory: kafka_2.8.0-.8.1.tgz.md5
Martin
On 8 Mar 2
SIGTERM.
- Martin
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18846/#review36371
---
On March 6, 2014, 3:26 p.m., Mar
Some more inconsistent command-line options:
--clientId in kafka-simple-consumer-perf-test.sh and
kafka-simple-consumer-shell.sh
-name, -loggc and -daemon in kafka-run-class.sh and kafka-server-start.sh
(single dash instead of a double dash)
It's aesthetics, but I agree that it's important.
M
[
https://issues.apache.org/jira/browse/KAFKA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kleppmann updated KAFKA-1189:
Status: Patch Available (was: Open)
> kafka-server-stop.sh doesn't sto
[
https://issues.apache.org/jira/browse/KAFKA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922649#comment-13922649
]
Martin Kleppmann commented on KAFKA-1189:
-
This happens if the broker is sta
[
https://issues.apache.org/jira/browse/KAFKA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kleppmann updated KAFKA-1189:
Attachment: KAFKA-1189.patch
> kafka-server-stop.sh doesn't sto
[
https://issues.apache.org/jira/browse/KAFKA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922642#comment-13922642
]
Martin Kleppmann commented on KAFKA-1189:
-
Created reviewboard h
/browse/KAFKA-1189
Repository: kafka
Description
---
KAFKA-1189 use SIGTERM to shut down broker, as nohup swallows SIGINT
Diffs
-
bin/kafka-server-stop.sh 35a26a6529a91e0e5b18c7a3e0357f9241b36721
Diff: https://reviews.apache.org/r/18846/diff/
Testing
---
Thanks,
Martin
I would be open to discussing it as a third alternative too.
> If we decide we do want to use this code for metrics then we may want to
> implement a sampling histogram either in addition to or as a replacement
> for the existing histograms and if you were up to contribute your
> impleme
Not sure if you want yet another opinion added to the pile -- but since I had a
similar problem on another project recently, I thought I'd weigh in. (On that
project we were originally using Coda's library, but then switched to rolling
our own metrics implementation because we needed to do a few
14 matches
Mail list logo
