GitHub user bbonnin opened a pull request:

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

    [ZEPPELIN-1537] Elasticsearch improvement for results of aggregations

    ### What is this PR for?
    The result of an aggregation query returned by the interpreter contains 
only "key" and "doc_count" in case of a multi-buckets aggregations.
    But the result returned by Elasticsearch can contain more data according to 
the query.
    This PR is an improvement of the result returned by the interpreter.
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    * [X] - Dev of the improvement in the interpreter
    * [X] - Add a test case 
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1537
    
    ### How should this be tested?
    In a paragraph, enter a query with multiple aggregations:
    search /logs { "aggs" : { 
                "length" : { "terms": { "field": "status" }, 
                "aggs" : { "sum_length" : { "sum" : { "field" : 
"content_length" } } } } }
    
    ### 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/bbonnin/zeppelin master

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

    https://github.com/apache/zeppelin/pull/1508.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 #1508
    
----
commit a0a7bb9f3773340b9916f650fcbee5af8178fc21
Author: Bruno Bonnin <bbon...@gmail.com>
Date:   2016-10-12T21:20:25Z

    Elasticsearch improvement for results of aggregations

----


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