From c7982e70cbe5072758fd45459b8ab44b4d024e4f Mon Sep 17 00:00:00 2001 From: repat Date: Thu, 11 Dec 2014 00:30:41 +0100 Subject: [PATCH] typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f9173fdf..bebea669 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ It is implemented as an [Elasticsearch plugin](http://www.elasticsearch.org/guid The JDBC plugin was designed for tabular data. If you have tables with many joins, the JDBC plugin is limited in the way to reconstruct deeply nested objects to JSON and process object semantics like object identity. -Though it would be possible to extend the JDBC plugin with a maaping feature where all the object properties +Though it would be possible to extend the JDBC plugin with a mapping feature where all the object properties could be specified, the current solution is focused on rather simple tabular data streams. Creating a JDBC river is easy: