GitHub user AhyoungRyu opened a pull request:

    https://github.com/apache/zeppelin/pull/1162

    [ZEPPELIN-909] Apply new mechanism to Elasticsearch interpreter

    ### What is this PR for?
    This PR applies the [new interpreter registration 
mechanism](https://issues.apache.org/jira/browse/ZEPPELIN-804) to Elasticsearch 
interpreter.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * [x] - Remove static property definition code lines in 
`ElasticsearchInterpreter.java` and create `interpreter-setting.json` under 
`elasticsearch/src/main/resources`
    
    ### What is the Jira issue?
    [ZEPPELIN-909](https://issues.apache.org/jira/browse/ZEPPELIN-909)
    
    ### How should this be tested?
    1. apply this patch
    2. rm -r `interpreter/elasticsearch` and rm `conf/interpreter.json`
    3. build source
    4. bin/zeppelin-daemon.sh start
    5. Run a paragraph with elasticsearch commands 
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/AhyoungRyu/zeppelin ZEPPELIN-909

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1162.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 #1162
    
----
commit f1c11565c7f75f9de0f9cc997385c4237e934030
Author: AhyoungRyu <fbdkdu...@hanmail.net>
Date:   2016-07-11T04:45:15Z

    Apply new mechanism to Elasticsearch interpreter

commit 76ac45d69626fe2260130afe5c36c2f390f152ba
Author: AhyoungRyu <fbdkdu...@hanmail.net>
Date:   2016-07-11T04:46:38Z

    Remove static block

----


---
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.
---

Reply via email to