Repository: zeppelin
Updated Branches:
  refs/heads/branch-0.6 779826528 -> 5d66a5c02


[ZEPPELIN-1031] Update Elasticsearch to release 2.3.3

### What is this PR for?
Update ElasticSearch interpreter to use ElasticSearch 2.3.3

### What type of PR is it?
[Improvement]

### What is the Jira issue?
[ZEPPELIN-1031](https://issues.apache.org/jira/browse/ZEPPELIN-1031)

Author: Luciano Resende <[email protected]>

Closes #1040 from lresende/elasticsearch and squashes the following commits:

67cc853 [Luciano Resende] [ZEPPELIN-1031] Update Elasticsearch to release 2.3.3

(cherry picked from commit c590649a675eb7e107945c4ff0264599fdf10700)
Signed-off-by: Mina Lee <[email protected]>


Project: http://git-wip-us.apache.org/repos/asf/zeppelin/repo
Commit: http://git-wip-us.apache.org/repos/asf/zeppelin/commit/5d66a5c0
Tree: http://git-wip-us.apache.org/repos/asf/zeppelin/tree/5d66a5c0
Diff: http://git-wip-us.apache.org/repos/asf/zeppelin/diff/5d66a5c0

Branch: refs/heads/branch-0.6
Commit: 5d66a5c02318ec1563d657f8909424f053b27b59
Parents: 7798265
Author: Luciano Resende <[email protected]>
Authored: Fri Jun 17 10:58:09 2016 -0700
Committer: Mina Lee <[email protected]>
Committed: Sun Jun 26 09:23:39 2016 -0700

----------------------------------------------------------------------
 elasticsearch/pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/zeppelin/blob/5d66a5c0/elasticsearch/pom.xml
----------------------------------------------------------------------
diff --git a/elasticsearch/pom.xml b/elasticsearch/pom.xml
index b26dad6..95b25a2 100644
--- a/elasticsearch/pom.xml
+++ b/elasticsearch/pom.xml
@@ -34,7 +34,7 @@
   <url>http://www.apache.org</url>
 
   <properties>
-    <elasticsearch.version>2.1.0</elasticsearch.version>
+    <elasticsearch.version>2.3.3</elasticsearch.version>
     <guava.version>18.0</guava.version>
     <json-flattener.version>0.1.6</json-flattener.version>
   </properties>

Reply via email to