Skip to content
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

Fix NPE when running a range query on a `scaled_float` with no upper bound. #20253

Merged
merged 1 commit into from Sep 1, 2016

Conversation

Projects
None yet
4 participants
@jpountz
Copy link
Contributor

commented Aug 31, 2016

The null check was there, but on the wrong variable.

@s1monw

This comment has been minimized.

Copy link
Contributor

commented Aug 31, 2016

LGTM

@jasontedor

This comment has been minimized.

Copy link
Member

commented Aug 31, 2016

LGTM.

Fix NPE when running a range query on a `scaled_float` with no upper …
…bound. #20253

The null check was there, but on the wrong variable.

@jpountz jpountz force-pushed the jpountz:fix/range_on_scaled_float branch to 34aaea6 Sep 1, 2016

@jpountz jpountz merged commit 34aaea6 into elastic:master Sep 1, 2016

1 of 2 checks passed

elasticsearch-ci Build started sha1 is merged.
Details
CLA Commit author is a member of Elasticsearch
Details

@jpountz jpountz deleted the jpountz:fix/range_on_scaled_float branch Sep 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.