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

BytesReference usage to properly work when hasArray is not available #5455

Closed
wants to merge 1 commit into from

Conversation

kimchy
Copy link
Member

@kimchy kimchy commented Mar 18, 2014

when a BytesReference doesn't have a backing array, properly handle the case in places where its applicable

when a BytesReference doesn't have a backing array, properly handle the case in places where its applicable
@uboness
Copy link
Contributor

uboness commented Mar 18, 2014

LGTM, just make sure to open an issue for the todo in the FsTranslog

@@ -341,6 +341,9 @@ protected void parseCreateField(ParseContext context, List<Field> fields) throws
}
}
}
if (!source.hasArray()) {
source = source.toBytesArray();
}
assert source.hasArray();
Copy link
Contributor

Choose a reason for hiding this comment

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

does this assert still make sense?

@kimchy kimchy closed this in 0f6c24d Mar 18, 2014
kimchy added a commit that referenced this pull request Mar 18, 2014
when a BytesReference doesn't have a backing array, properly handle the case in places where its applicable
closes #5455
@kimchy
Copy link
Member Author

kimchy commented Mar 18, 2014

@s1monw missed your notes, pushed, sorry!, will fix the additional notes

@s1monw
Copy link
Contributor

s1monw commented Mar 18, 2014

@kimchy thx

@kimchy
Copy link
Member Author

kimchy commented Mar 19, 2014

issue for translog added: #5463, and pushed

@kimchy kimchy deleted the fix_byte_array branch August 18, 2014 22:15
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.

None yet

4 participants