You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by go...@apache.org on 2019/02/06 21:40:27 UTC
[storm] 05/12: MINOR: Remove unused parameter from
storm-kafka-client-example docs
This is an automated email from the ASF dual-hosted git repository.
govind pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git
commit e93e00c57b108dd6ee57ac2f133ba93b29b24c79
Author: Stig Rohde Døssing <sr...@apache.org>
AuthorDate: Fri Jan 11 11:58:05 2019 +0100
MINOR: Remove unused parameter from storm-kafka-client-example docs
---
examples/storm-kafka-client-examples/README.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/examples/storm-kafka-client-examples/README.markdown b/examples/storm-kafka-client-examples/README.markdown
index 4ece9ec..d4c28a1 100644
--- a/examples/storm-kafka-client-examples/README.markdown
+++ b/examples/storm-kafka-client-examples/README.markdown
@@ -1,10 +1,10 @@
## Usage
This module contains example topologies demonstrating storm-kafka-client spout and Trident usage. Please ensure you have a Kafka instance running at localhost:9092 before you deploy the topologies.
-The module is built by running `mvn clean package -Dstorm.kafka.artifact.id=<kafka_artifact_id> -Dstorm.kafka.client.version=<kafka_broker_version>`, where the two properties should match the Kafka brokers you want to connect to. For example, for Kafka 0.11.0.0 the `<kafka_artifact_id>` might be `kafka_2.12` and `<kafka_broker_version>` would be `0.11.0.0`. This will generate the `target/storm-kafka-client-examples-VERSION.jar` file. The jar contains all dependencies and can be submitted [...]
+The module is built by running `mvn clean package -Dstorm.kafka.client.version=<kafka_broker_version>`, where the property should match the Kafka version you want to use. For example, for Kafka 0.11.0.0 the `<kafka_broker_version>` would be `0.11.0.0`. This will generate the `target/storm-kafka-client-examples-VERSION.jar` file. The jar contains all dependencies and can be submitted to Storm via the Storm CLI, e.g.
```
storm jar storm-kafka-client-examples-2.0.0-SNAPSHOT.jar org.apache.storm.kafka.spout.KafkaSpoutTopologyMainNamedTopics
```
will submit the topologies set up by KafkaSpoutTopologyMainNamedTopics to Storm.
-Note that this example produces a jar containing all dependencies for ease of use. In a production environment you may want to reduce the jar size by extracting some dependencies (e.g. `org.apache.kafka:kafka-clients`) from the jar. You can do this by setting the dependencies you don't want to include in the jars to `provided` scope, and then using the `--artifacts` flag for the `storm jar` command to fetch the dependencies when submitting the topology. See the [CLI documentation](http:/ [...]
\ No newline at end of file
+Note that this example produces a jar containing all dependencies for ease of use. When you deploy your own topologies in a production environment you may want to reduce the jar size by extracting some dependencies (e.g. `org.apache.kafka:kafka-clients`) from the jar. You can do this by setting the dependencies you don't want to include in the jars to `provided` scope, and then using the `--artifacts` flag for the `storm jar` command to fetch the dependencies when submitting the topology [...]
\ No newline at end of file