GitHub user bbonnin opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/596
Display aggregation result with Elasticsearch interpreter
### What is this PR for?
Take into account the aggregations with Elastisearch search query.
This improvement of the interpreter will return the result of the
aggregation part if any in the result of search query.
### What type of PR is it?
Improvement
### Todos
* [X ] - Modify interpreter to read and return the aggregation result if any
* [X ] - Update docs
### Is there a relevant Jira issue?
No
### How should this be tested?
Test with an Elasticsearch and with examples provided in the doc.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? elasticsearch.md
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbonnin/incubator-zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/596.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 #596
----
commit 6f76ffd323432cdb6fad9e9a9c9fcf1f1fee6f97
Author: Bruno Bonnin <[email protected]>
Date: 2015-12-28T14:36:53Z
Support of aggregation results
commit 17f4e58ccf832f1a40e34f1f97425167bc979af3
Author: Bruno Bonnin <[email protected]>
Date: 2015-12-28T14:37:30Z
Merge branch 'master' of https://github.com/bbonnin/incubator-zeppelin
commit 6793232b228bcee5e9422f4e7b84933e5f2fc625
Author: Bruno Bonnin <[email protected]>
Date: 2015-12-28T14:46:41Z
Update elasticsearch.md
commit aa809e2d7fcd2ecedd4d1e1348a9fb2e1e51ce80
Author: Bruno Bonnin <[email protected]>
Date: 2015-12-28T14:47:42Z
Update elasticsearch.md
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---