[metamodel] 03/05: Fixed typo.

[arjansh]

This is an automated email from the ASF dual-hosted git repository.

arjansh pushed a commit to annotated tag MetaModel-5.3.3-HI1
in repository https://gitbox.apache.org/repos/asf/metamodel.git

commit 3ae1d7c774dd3eb8ef77d151f10cad540a603772
Author: Arjan Seijkens <a.seijk...@quadient.com>
AuthorDate: Tue Jul 7 07:57:58 2020 +0200

    Fixed typo.
---
 .../org/apache/metamodel/elasticsearch/common/ElasticSearchUtils.java   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/elasticsearch/common/src/main/java/org/apache/metamodel/elasticsearch/common/ElasticSearchUtils.java
 
b/elasticsearch/common/src/main/java/org/apache/metamodel/elasticsearch/common/ElasticSearchUtils.java
index 57ca7a1..f5c70e8 100644
--- 
a/elasticsearch/common/src/main/java/org/apache/metamodel/elasticsearch/common/ElasticSearchUtils.java
+++ 
b/elasticsearch/common/src/main/java/org/apache/metamodel/elasticsearch/common/ElasticSearchUtils.java
@@ -293,7 +293,7 @@ public class ElasticSearchUtils {
                     } else if (column.getType() == ColumnType.MAP && value == 
null) {
                         // Because of a bug in Elasticsearch, when field names 
contain dots, it's possible that the
                         // mapping of the index described a column to be of 
the type "MAP", while it's based on a number
-                        // of fields contains dots in their name. In this case 
we may have to work around that
+                        // of fields containing dots in their name. In this 
case we may have to work around that
                         // inconsistency by creating column names with dots 
ourselves, based on the schema.
                         final Map<String, Object> valueMap = new HashMap<>();