Skip to content

[ZEPPELIN-1537] Elasticsearch improvement for results of aggregations - #1508

Closed
bbonnin wants to merge 1 commit into
apache:masterfrom
bbonnin:master
Closed

[ZEPPELIN-1537] Elasticsearch improvement for results of aggregations#1508
bbonnin wants to merge 1 commit into
apache:masterfrom
bbonnin:master

Conversation

@bbonnin

Copy link
Copy Markdown
Contributor

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

  • - Dev of the improvement in the interpreter
  • - 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

@bzz

bzz commented Oct 17, 2016

Copy link
Copy Markdown
Member

Looks good to me, 👍 for tests!

Merging if there is no further discussion.

darionyaphet pushed a commit to darionyaphet/zeppelin that referenced this pull request Oct 27, 2016
### 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
Author: Bruno Bonnin <bbonnin@gmail.com>
Closesapache#1508 from bbonnin/master and squashes the following commits:
a0a7bb9 [Bruno Bonnin] Elasticsearch improvement for results of aggregations
pedrozatta pushed a commit to pedrozatta/zeppelin that referenced this pull request Oct 27, 2016
### 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
Author: Bruno Bonnin <bbonnin@gmail.com>
Closesapache#1508 from bbonnin/master and squashes the following commits:
a0a7bb9 [Bruno Bonnin] Elasticsearch improvement for results of aggregations
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@bbonnin@bzz