Skip to content

Add REST tests for percentiles agg #26266

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
Aug 18, 2017

Conversation

polyfractal
Copy link
Contributor

There's a separate test for each of TDigest and HDR Histo to keep things clean. The two sets are essentially identical, with different values depending on the algo. And HDR Histo has an extra test for negative numbers

Related to #26220

There's a separate test for each TDigest and HDR Histo,
to keep things clean.

Related to elastic#26220
@polyfractal polyfractal added review >test Issues or PRs that are addressing/adding tests labels Aug 17, 2017
50.0: 76.0

---
"Non-keyed test":
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure the word "test" buys anything in the test name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

But how are we supposed to know it's a test?!

Hehe, point taken. Will amend on the next batch :)

@polyfractal polyfractal merged commit 9f295b4 into elastic:master Aug 18, 2017
polyfractal added a commit that referenced this pull request Aug 18, 2017
There's a separate test for each TDigest and HDR Histo,
to keep things clean.

Related to #26220
polyfractal added a commit that referenced this pull request Aug 18, 2017
There's a separate test for each TDigest and HDR Histo,
to keep things clean.

Related to #26220
50.0: 51.0302734375
- match:
aggregations.percentiles_double.values:
5.0: 1.0
Copy link
Contributor

Choose a reason for hiding this comment

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

I tink these values need to be quoted

"5.0": 1.0

Cause this is failing in the python client.

Copy link
Contributor

Choose a reason for hiding this comment

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

That is consistent with the documentation for all versions I checked, from v5.3 though master, as well as 2.4 and 1.7. Seems like the test is wrong.

@lcawl lcawl removed the v6.1.0 label Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests v6.0.0-beta2 v7.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants