GitHub user 1ambda opened a pull request: https://github.com/apache/zeppelin/pull/1598
[ZEPPELIN-1618] [WIP] Support ElasticSearch 5.0 ### What is this PR for? ElasticSearch just released in Oct 26 and It requires 5.x client driver but zeppelin currently use 2.x only. - we need 2 different profiles for 2.x and 5.x (there are no 3.x, 4.x) - 5.x client require different codebase. In this case we should keep 2 version of code at the same time like the spark code. - 5.x client requires JAVA 8 at least ### What type of PR is it? Improvement ### Todos * [ ] - create profiles for 2.x and 5.x * [ ] - setup JAVA 8 validation for 5.x * [ ] - create the 5.x interpreter * [ ] - update license * [ ] - update docs (build, usage) * [ ] - update default `elasticsearch.version` to 2.4.x (the most recent for 2.x) ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-1618 ### How should this be tested? Some tests will be included. ### Screenshots (if appropriate) <img width="404" alt="screen shot 2016-11-04 at 9 46 23 pm" src="https://cloud.githubusercontent.com/assets/4968473/20006211/ef9d9f96-a2d9-11e6-9b89-efc8f38b7acf.png"> <img width="828" alt="elasticsearch" src="https://cloud.githubusercontent.com/assets/4968473/20006213/f1053236-a2d9-11e6-80ab-e9e4c954bb64.png"> ### Questions: * Does the licenses files need update? - YES * Is there breaking changes for older versions? - NO * Does this needs documentation? - YES You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin feat/support-es-5.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1598.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1598 ---- commit d973cdece3175c7ca16dccf752f51516fb1efe59 Author: 1ambda <1am...@gmail.com> Date: 2016-11-04T12:55:11Z chore: Create elastic profile 2, 5 ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---