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

Return 0 instead of -1 for unknown/non-exposed ramBytesUsed() #8291

Merged
merged 1 commit into from Nov 3, 2014

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Oct 30, 2014

From @rmuir - "The accountable interface specifies that such values are illegal"

Fixes #8239

@rjernst
Copy link
Member

rjernst commented Oct 31, 2014

What about in BinaryDVNumericIndexFieldData, NumericDVIndexFieldData? I see anonymous instance of AtomicDoubleFieldData that initializes ramBytesUsed to -1.

Also SortedNumericDoubleFieldData, SortedNumericFloatFieldData and SortedNumericLongFieldData call super() with -1.

@dakrone
Copy link
Member Author

dakrone commented Nov 3, 2014

I fixed the other invocations, thanks for taking a look @rjernst !

@rjernst
Copy link
Member

rjernst commented Nov 3, 2014

LGTM.

@dakrone dakrone force-pushed the 8239-no-negative-ramBytesUsed branch from f6a7342 to a6d7742 Compare November 3, 2014 16:06
The accountable interface specifies that such values are illegal

Fixes elastic#8239
@dakrone dakrone merged commit a6d7742 into elastic:master Nov 3, 2014
@dakrone dakrone added the :Core/Infra/Core Core issues without another label label Nov 5, 2014
@dakrone dakrone deleted the 8239-no-negative-ramBytesUsed branch November 11, 2014 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Core/Infra/Core Core issues without another label v1.5.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Don't use negative ramBytesUsed() values.
3 participants