You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ch...@apache.org on 2018/10/26 15:06:23 UTC
[flink] branch master updated: [hotfix][docs] Fix various typos
This is an automated email from the ASF dual-hosted git repository.
chesnay pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new 43afd09 [hotfix][docs] Fix various typos
43afd09 is described below
commit 43afd09ea673a3ac99741f6fc5ff80d492f55648
Author: Manuel Hoffmann <ma...@manuel-hoffmann.info>
AuthorDate: Fri Oct 26 17:06:14 2018 +0200
[hotfix][docs] Fix various typos
---
docs/dev/batch/hadoop_compatibility.md | 2 +-
docs/dev/connectors/cassandra.md | 2 +-
docs/dev/table/connect.md | 6 +++---
docs/dev/table/sqlClient.md | 2 +-
docs/dev/table/streaming/temporal_tables.md | 2 +-
docs/dev/table/tableApi.md | 2 +-
6 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/docs/dev/batch/hadoop_compatibility.md b/docs/dev/batch/hadoop_compatibility.md
index c665b5d..4e48182 100644
--- a/docs/dev/batch/hadoop_compatibility.md
+++ b/docs/dev/batch/hadoop_compatibility.md
@@ -75,7 +75,7 @@ if you only want to use your Hadoop data types. See the
To use Hadoop `InputFormats` with Flink the format must first be wrapped
using either `readHadoopFile` or `createHadoopInput` of the
-`HadoopInputs` utilty class.
+`HadoopInputs` utility class.
The former is used for input formats derived
from `FileInputFormat` while the latter has to be used for general purpose
input formats.
diff --git a/docs/dev/connectors/cassandra.md b/docs/dev/connectors/cassandra.md
index c4c3e3a..2a2acb3 100644
--- a/docs/dev/connectors/cassandra.md
+++ b/docs/dev/connectors/cassandra.md
@@ -77,7 +77,7 @@ The following configuration methods can be used:
* Allows exactly-once processing for non-deterministic algorithms.
6. _setFailureHandler([CassandraFailureHandler failureHandler])_
* An __optional__ setting
- * Sets the custom failur handler.
+ * Sets the custom failure handler.
7. _build()_
* Finalizes the configuration and constructs the CassandraSink instance.
diff --git a/docs/dev/table/connect.md b/docs/dev/table/connect.md
index b413390..5f11127 100644
--- a/docs/dev/table/connect.md
+++ b/docs/dev/table/connect.md
@@ -83,7 +83,7 @@ The **connector** describes the external system that stores the data of a table.
Some systems support different **data formats**. For example, a table that is stored in Kafka or in files can encode its rows with CSV, JSON, or Avro. A database connector might need the table schema here. Whether or not a storage system requires the definition of a format, is documented for every [connector](connect.html#table-connectors). Different systems also require different [types of formats](connect.html#table-formats) (e.g., column-oriented formats vs. row-oriented formats). The [...]
-The **table schema** defines the schema of a table that is exposed to SQL queries. It describes how a source maps the data format to the table schema and a sink vice versa. The schema has access to fields defined by the connector or format. It can use one or more fields for extracting or inserting [time attributes](streaming/time_attributes.html). If input fields have no determinstic field order, the schema clearly defines column names, their order, and origin.
+The **table schema** defines the schema of a table that is exposed to SQL queries. It describes how a source maps the data format to the table schema and a sink vice versa. The schema has access to fields defined by the connector or format. It can use one or more fields for extracting or inserting [time attributes](streaming/time_attributes.html). If input fields have no deterministic field order, the schema clearly defines column names, their order, and origin.
The subsequent sections will cover each definition part ([connector](connect.html#table-connectors), [format](connect.html#table-formats), and [schema](connect.html#table-schema)) in more detail. The following example shows how to pass them:
@@ -113,7 +113,7 @@ schema: ...
The table's type (`source`, `sink`, or `both`) determines how a table is registered. In case of table type `both`, both a table source and table sink are registered under the same name. Logically, this means that we can both read and write to such a table similarly to a table in a regular DBMS.
-For streaming queries, an [update mode](connect.html#update-mode) declares how to communicate between a dynamic table and the storage system for continous queries.
+For streaming queries, an [update mode](connect.html#update-mode) declares how to communicate between a dynamic table and the storage system for continuous queries.
The following code shows a full example of how to connect to Kafka for reading Avro records.
@@ -673,7 +673,7 @@ connector:
# (only MB granularity is supported)
interval: 60000 # optional: bulk flush interval (in milliseconds)
back-off: # optional: backoff strategy ("disabled" by default)
- type: ... # valid strategis are "disabled", "constant", or "exponential"
+ type: ... # valid strategies are "disabled", "constant", or "exponential"
max-retries: 3 # optional: maximum number of retries
delay: 30000 # optional: delay between each backoff attempt (in milliseconds)
diff --git a/docs/dev/table/sqlClient.md b/docs/dev/table/sqlClient.md
index 2b1c089..d4eb228 100644
--- a/docs/dev/table/sqlClient.md
+++ b/docs/dev/table/sqlClient.md
@@ -490,7 +490,7 @@ tables:
WHERE MyField2 > 200
{% endhighlight %}
-Similar to table sources and sinks, views defined in a session environment file have highest precendence.
+Similar to table sources and sinks, views defined in a session environment file have highest precedence.
Views can also be created within a CLI session using the `CREATE VIEW` statement:
diff --git a/docs/dev/table/streaming/temporal_tables.md b/docs/dev/table/streaming/temporal_tables.md
index 2dd6ed7..b450527 100644
--- a/docs/dev/table/streaming/temporal_tables.md
+++ b/docs/dev/table/streaming/temporal_tables.md
@@ -114,7 +114,7 @@ Each query to `Rates(timeAttribute)` would return the state of the `Rates` for t
**Note**: Currently, Flink doesn't support directly querying the temporal table functions with a constant time attribute parameter. At the moment, temporal table functions can only be used in joins.
The example above was used to provide an intuition about what the function `Rates(timeAttribute)` returns.
-See also the [joining page for continous queries](joins.html) for more information about how to join with a temporal table.
+See also the [joining page for continuous queries](joins.html) for more information about how to join with a temporal table.
### Defining Temporal Table Function
diff --git a/docs/dev/table/tableApi.md b/docs/dev/table/tableApi.md
index 6c4e1be..76bd5b2 100644
--- a/docs/dev/table/tableApi.md
+++ b/docs/dev/table/tableApi.md
@@ -1317,7 +1317,7 @@ val table = input
</div>
</div>
-Window properties such as the start, end, or rowtime timestamp of a time window can be added in the select statement as a property of the window alias as `w.start`, `w.end`, and `w.rowtime`, respectively. The window start and rowtime timestamps are the inclusive lower and uppper window boundaries. In contrast, the window end timestamp is the exclusive upper window boundary. For example a tumbling window of 30 minutes that starts at 2pm would have `14:00:00.000` as start timestamp, `14:29 [...]
+Window properties such as the start, end, or rowtime timestamp of a time window can be added in the select statement as a property of the window alias as `w.start`, `w.end`, and `w.rowtime`, respectively. The window start and rowtime timestamps are the inclusive lower and upper window boundaries. In contrast, the window end timestamp is the exclusive upper window boundary. For example a tumbling window of 30 minutes that starts at 2pm would have `14:00:00.000` as start timestamp, `14:29: [...]
<div class="codetabs" markdown="1">
<div data-lang="java" markdown="1">