GitHub user mosuka opened a pull request:

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

    [ZEPPELIN-1038] Add Solr interpreter

    ### What is this PR for?
    A few sentences describing the overall goals of the pull request's commits.
    First time? Check out the contributing guide - 
https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md
    
    Solr 6.1.0 that supports the SQL has been released. I propose to add 
interpreter to Zeppelin.
    It is a PR for facilitate the visualization and analysis of the index of 
Solr with Zeppelin.
    
    ### What type of PR is it?
    Feature
    
    ### Todos
    * [x] - PR
    * [x] - Unit-test
    * [x] - Document
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1038
    
    ### How should this be tested?
    Added unit-tests, also manual testing with sample data.
    
    ```
    $ mvn clean test -pl zeppelin-interpreter -pl solr
    [INFO] Scanning for projects...
    
    [...]
    
    -------------------------------------------------------
     T E S T S
    -------------------------------------------------------
    Running org.apache.zeppelin.solr.SolrSqlInterpreterTest
    Creating dataDir: 
/private/var/folders/99/p369dv7n5sqdl9rdvyx0vqzr0000gn/T/org.apache.zeppelin.solr.SolrSqlInterpreterTest_589C7DC8E23A0BDC-001/init-core-data-001
    log4j:WARN No appenders could be found for logger 
(org.eclipse.jetty.util.log).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for 
more info.
    Jun 21, 2016 9:36:10 AM 
com.carrotsearch.randomizedtesting.ThreadLeakControl checkThreadLeaks
    WARNING: Will linger awaiting termination of 1 leaked thread(s).
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.744 sec 
- in org.apache.zeppelin.solr.SolrSqlInterpreterTest
    
    Results :
    
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
    
    [INFO] 
------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO]
    [INFO] Zeppelin: Interpreter .............................. SUCCESS [02:31 
min]
    [INFO] Zeppelin: Solr interpreter ......................... SUCCESS [ 
19.532 s]
    [INFO] 
------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] 
------------------------------------------------------------------------
    [INFO] Total time: 02:51 min
    [INFO] Finished at: 2016-06-21T09:36:11+09:00
    [INFO] Final Memory: 57M/578M
    [INFO] 
------------------------------------------------------------------------
    ```
    
    ### Screenshots (if appropriate)
    
    
![solr-config](https://cloud.githubusercontent.com/assets/970948/16214506/db4d42d2-3793-11e6-9a3c-28f0b6349aef.png)
    
    
![solr-enabling-interpreter](https://cloud.githubusercontent.com/assets/970948/16214510/e6adca98-3793-11e6-9c1c-1a504920d0a7.png)
    
    
![solr-sample](https://cloud.githubusercontent.com/assets/970948/16214512/ebf99cfc-3793-11e6-91c9-155a0e9053bb.png)
    
    ### Questions:
    * Does this needs more detailed documention?

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

    $ git pull https://github.com/mosuka/incubator-zeppelin master

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

    https://github.com/apache/zeppelin/pull/1054.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 #1054
    
----
commit 42a921db599d47fd87685efedf94589c76cce850
Author: Minoru Osuka <minoru.os...@gmail.com>
Date:   2016-06-21T00:15:54Z

    [ZEPPELIN-1038] Add Solr interpreter

----


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