You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by xi...@apache.org on 2023/01/09 10:53:48 UTC
[storm] branch master updated: [hotfix] fix typo
This is an automated email from the ASF dual-hosted git repository.
xinwang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git
The following commit(s) were added to refs/heads/master by this push:
new 05037e2cf [hotfix] fix typo
new bf29d1cc9 Merge pull request #3508 from wuyouwuyoulian/typofix
05037e2cf is described below
commit 05037e2cffd0000f106f68f16fae2357a1dec4ba
Author: wuyouwuyoulian <xq...@163.com>
AuthorDate: Mon Jan 9 11:06:22 2023 +0800
[hotfix] fix typo
---
docs/Metrics.md | 2 +-
docs/Multilang-protocol.md | 2 +-
docs/Stream-API.md | 2 +-
docs/Windowing.md | 2 +-
docs/storm-hive.md | 2 +-
docs/storm-jms-example.md | 8 ++++----
docs/storm-jms-spring.md | 2 +-
flux/flux-core/src/test/resources/configs/bad_hbase.yaml | 2 +-
8 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/docs/Metrics.md b/docs/Metrics.md
index dcf8fac58..6137f0943 100644
--- a/docs/Metrics.md
+++ b/docs/Metrics.md
@@ -47,7 +47,7 @@ topology.metrics.consumer.register:
argument: "http://example.com:8080/metrics/my-topology/"
```
-Storm adds a MetricsConsumerBolt to your topolology for each class in the `topology.metrics.consumer.register` list. Each MetricsConsumerBolt subscribes to receive metrics from all tasks in the topology. The parallelism for each Bolt is set to `parallelism.hint` and `component id` for that Bolt is set to `__metrics_<metrics consumer class name>`. If you register the same class name more than once, postfix `#<sequence number>` is appended to component id.
+Storm adds a MetricsConsumerBolt to your topology for each class in the `topology.metrics.consumer.register` list. Each MetricsConsumerBolt subscribes to receive metrics from all tasks in the topology. The parallelism for each Bolt is set to `parallelism.hint` and `component id` for that Bolt is set to `__metrics_<metrics consumer class name>`. If you register the same class name more than once, postfix `#<sequence number>` is appended to component id.
Storm provides some built-in metrics consumers for you to try out to see which metrics are provided in your topology.
diff --git a/docs/Multilang-protocol.md b/docs/Multilang-protocol.md
index be12b1921..ae77b1990 100644
--- a/docs/Multilang-protocol.md
+++ b/docs/Multilang-protocol.md
@@ -7,7 +7,7 @@ This page explains the multilang protocol as of Storm 0.7.1. Versions prior to 0
# Storm Multi-Language Protocol
-## Supported Lanugages
+## Supported Languages
Storm Multi-Language has implementation in the following languages:
diff --git a/docs/Stream-API.md b/docs/Stream-API.md
index fb381a490..06e3e367e 100644
--- a/docs/Stream-API.md
+++ b/docs/Stream-API.md
@@ -204,7 +204,7 @@ Stream<Long> sums = numbers.window(TumblingWindows.of(Duration.seconds(10)).aggr
Stream<Long> sums = numbers.window(...).reduce((x, y) -> x + y);
```
-`aggreagate` and `reduce` differs in the way in which the aggreate results are computed.
+`aggregate` and `reduce` differs in the way in which the aggregate results are computed.
A `reduce` operation repeatedly applies the given reducer and reduces two values to a single value until there is only one value left. This may not be feasible or easy for all kinds of aggreagations (e.g. avg).
diff --git a/docs/Windowing.md b/docs/Windowing.md
index 848bc9733..bf625d260 100644
--- a/docs/Windowing.md
+++ b/docs/Windowing.md
@@ -251,7 +251,7 @@ e10 is not evaluated since the tuple ts `8:00:39` is beyond the watermark time `
The window calculation considers the time gaps and computes the windows based on the tuple timestamp.
## Guarantees
-The windowing functionality in storm core currently provides at-least once guarentee. The values emitted from the bolts
+The windowing functionality in storm core currently provides at-least once guarantee. The values emitted from the bolts
`execute(TupleWindow inputWindow)` method are automatically anchored to all the tuples in the inputWindow. The downstream
bolts are expected to ack the received tuple (i.e the tuple emitted from the windowed bolt) to complete the tuple tree.
If not the tuples will be replayed and the windowing computation will be re-evaluated.
diff --git a/docs/storm-hive.md b/docs/storm-hive.md
index 9da4a8ec2..c44020432 100644
--- a/docs/storm-hive.md
+++ b/docs/storm-hive.md
@@ -33,7 +33,7 @@ HiveBolt hiveBolt = new HiveBolt(hiveOptions);
### RecordHiveMapper
This class maps Tuple field names to Hive table column names.
- There are two implementaitons available
+ There are two implementations available
+ DelimitedRecordHiveMapper (org.apache.storm.hive.bolt.mapper.DelimitedRecordHiveMapper)
diff --git a/docs/storm-jms-example.md b/docs/storm-jms-example.md
index 29cadf100..36caf5eb4 100644
--- a/docs/storm-jms-example.md
+++ b/docs/storm-jms-example.md
@@ -16,8 +16,8 @@ information about the tuples it receives and emits).
Grey arrows represent JMS messages, while black arrows represent the flow of Storm tuple objects.
-### JMS Transactions and Gauranteed Processing
-The example is set up to be "transactional," meaning the JMS Spout will use Storm's guranteed
+### JMS Transactions and Guaranteed Processing
+The example is set up to be "transactional," meaning the JMS Spout will use Storm's guaranteed
processing capabilities to determine if a JMS Message should be acknowledged. Each bolt in the
topology will anchor to each tuple it receives. If every bolt successfully processes and acks
each tuple in the chain, the original JMS Message will be acknowledged, and the underlying
@@ -34,12 +34,12 @@ another originating from a JMS Spout connected to a Topic.
1. The "JMS Queue Spout" receives a JMS Message object from the queue, and emits a
tuple to the "Intermediate Bolt"
2. The "Intermediate Bolt" emits a tuple to the "Final Bolt" and the "JMS Topic Bolt", and acks
-the tuple it recieved.
+the tuple it received.
3. The "Final Bolt" receives the tuple and simply acks it, it does not emit anything.
4. The "JMS Topic Bolt" receives a tuple, constructs a JMS Message from the tuple's values,
and publishes the message to a JMS Topic.
5. If the "JMS Topic Bolt" successfully publishes the JMS message, it will ack the tuple.
-6. The "JMS Queue Spout" will recieve notification if all bolts in the chain have acked
+6. The "JMS Queue Spout" will receive notification if all bolts in the chain have acked
and acknowledge the original JMS Message. If one or more bolts in the chain fail to ack a tuple, the
"JMS Queue Spout" will not acknowledge the JMS message.
diff --git a/docs/storm-jms-spring.md b/docs/storm-jms-spring.md
index 0428e3a63..df523aae8 100644
--- a/docs/storm-jms-spring.md
+++ b/docs/storm-jms-spring.md
@@ -5,7 +5,7 @@ documentation: true
---
###Connecting to JMS Using Spring's JMS Support
-Create a Spring applicationContext.xml file that defines one or more destination (topic/queue) beans, as well as a connecton factory.
+Create a Spring applicationContext.xml file that defines one or more destination (topic/queue) beans, as well as a connection factory.
<?xml version="1.0" encoding="UTF-8"?>
<beans
diff --git a/flux/flux-core/src/test/resources/configs/bad_hbase.yaml b/flux/flux-core/src/test/resources/configs/bad_hbase.yaml
index a29e31420..943a01beb 100644
--- a/flux/flux-core/src/test/resources/configs/bad_hbase.yaml
+++ b/flux/flux-core/src/test/resources/configs/bad_hbase.yaml
@@ -36,7 +36,7 @@ components:
- id: "counterFields"
className: "org.apache.storm.tuple.Fields"
constructorArgs:
- # !!! the following won't work, and should thow an IllegalArgumentException...
+ # !!! the following won't work, and should throw an IllegalArgumentException...
- "count"
- id: "mapper"