This is an automated email from the ASF dual-hosted git repository.
rubenql pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/calcite.git
The following commit(s) were added to refs/heads/master by this push:
new 67f3c5d Fix grammatical errors
67f3c5d is described below
commit 67f3c5d40130c76ddf22a587cab1f2640028c1fa
Author: Geetha Rangaswamaiah <[email protected]>
AuthorDate: Mon Sep 28 18:18:15 2020 +0530
Fix grammatical errors
---
site/_docs/algebra.md | 2 +-
site/_docs/druid_adapter.md | 2 +-
site/_docs/elasticsearch_adapter.md | 8 ++++----
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/site/_docs/algebra.md b/site/_docs/algebra.md
index 7310c53..7a1ba13 100644
--- a/site/_docs/algebra.md
+++ b/site/_docs/algebra.md
@@ -207,7 +207,7 @@ In this case, we create an EnumerableSort on top of the
input RelNode.
You can reference a field by name or ordinal.
Ordinals are zero-based. Each operator guarantees the order in which its output
-fields occur. For example, `Project` returns the fields in the generated by
+fields occur. For example, `Project` returns the fields generated by
each of the scalar expressions.
The field names of an operator are guaranteed to be unique, but sometimes that
diff --git a/site/_docs/druid_adapter.md b/site/_docs/druid_adapter.md
index 82db5a8..4442961 100644
--- a/site/_docs/druid_adapter.md
+++ b/site/_docs/druid_adapter.md
@@ -179,7 +179,7 @@ Currently there are two types:
but can be used to perform set operations as well.
In the model definition, there is an array of Strings called `complexMetrics`
that declares
-the alias for each complex metric defined. The alias is used in SQL, but it's
real column name
+the alias for each complex metric defined. The alias is used in SQL, but its
real column name
is used when Calcite generates the JSON query for druid.
# Foodmart data set
diff --git a/site/_docs/elasticsearch_adapter.md
b/site/_docs/elasticsearch_adapter.md
index bdf82c8..4163fbc 100644
--- a/site/_docs/elasticsearch_adapter.md
+++ b/site/_docs/elasticsearch_adapter.md
@@ -149,11 +149,11 @@ sqlline> SELECT _MAP['city'], _MAP['state'] from
"elasticsearch"."usa" order by
For queries without aggregate functions (like `COUNT`, `MAX` etc.) elastic
adapter
uses [scroll
API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-scroll.html),
by default.
-This ensures that consistent and full data-set is returned to end user (lazily
and in batches). Please note that
-scroll is automatically cleared (removed) when all query resuts are consumed.
+This ensures that consistent and full data-set is returned to the end user
(lazily and in batches). Please note that
+scroll is automatically cleared (removed) when all query results are consumed.
### Supported versions
-Currently this adapter supports ElasticSearch versions 6.x (or newer).
Generally
-we try to follow official [support
schedule](https://www.elastic.co/support/eol).
+Currently, this adapter supports ElasticSearch versions 6.x (or newer).
Generally,
+we try to follow the official [support
schedule](https://www.elastic.co/support/eol).
Also, types are not supported (this adapter only supports indices).
