Skip to content

Improving parsing of sigma param for Extended Stats Bucket Aggregation #17562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 10, 2016

Conversation

alexshadow007
Copy link
Contributor

Also improving parsing of percents param for Percentiles Bucket Aggregation
Fix for #17499

}
} else {
leftover.put(currentFieldName, parser.objectText());
parseToken(pipelineAggregatorName, parser, context, currentFieldName, token, params);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reason for using the leftover map here is so we can provide all the incorrect fields in one error message rather than reporting one error at a time and making the user potentially have to iterate multiple times to fix all their errors. Would you be able to revert these changes here so we again have these errors all reported in one go?

In the future I would like to extend this to the entire request and all parsing errors so we report all problems with the request at once.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually looking more at the changes you have made I see that you have made the code more like the other aggregation parsers so I think I would like to keep these changes and implement the above in another way in the future.

@colings86
Copy link
Contributor

@alexshadow007 Thanks for raising this PR. I left a couple of comments but I think this looks pretty good so far.

@clintongormley
Copy link
Contributor

@colings86 could review this again please?

@colings86
Copy link
Contributor

@alexshadow007 Sorry its taken a while for me to get back to you on this. It looks good to me but I wonder if you could update the branch with the latest master so it can be merged?

@alexshadow007
Copy link
Contributor Author

@colings86 I updated branch with latest master.

@colings86
Copy link
Contributor

@alexshadow007 Thanks. I'm just going to run through a build again to check there is nothing unexpected and then I'll merge it in

@colings86 colings86 merged commit 319ca82 into elastic:master May 10, 2016
@colings86
Copy link
Contributor

@alexshadow007 merged into master. Thanks for the contribution. Sorry it took so long to get reviewed and merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants