Skip to content

Conversation

@nastra
Copy link
Contributor

@nastra nastra commented May 4, 2023

No description provided.

Copy link
Contributor

@rdblue rdblue left a comment

Choose a reason for hiding this comment

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

My only nit is that we never want to directly call ByteBuffer#array(). We could replace that with ByteBuffers.toByteArray but we control the incoming buffer and know that it is always safe to call array() and use it without offsets. I think the only thing I'd change here is adding a comment that says something like "Calling array() is safe because the buffer is always allocated by the thread-local".

@nastra
Copy link
Contributor Author

nastra commented May 4, 2023

Agreed, it makes sense @rdblue to add a comment. I've done that and re-pushed. Thanks for reviewing

@nastra nastra force-pushed the spark-uuid-improvements branch from c7cb35d to ce8a1d2 Compare May 4, 2023 16:27
@nastra
Copy link
Contributor Author

nastra commented May 8, 2023

thanks for the review @rdblue, I've added a comment to make this clearer.

@nastra nastra merged commit fbdbaec into apache:master May 8, 2023
@nastra nastra deleted the spark-uuid-improvements branch May 8, 2023 06:49
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.

2 participants