You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched in the issues and found no similar issues.
What would you like to be improved?
Serialize and deserialize operations are not thread-safe in the BinaryRowDataSerializerWrapper.
Using the reuseRow and reuseWriter to serialize the RowData could speed the serialization process up, but it may lead to serializing incorrectly in multi-threads.
YesOrNo828
changed the title
[Improvement]:Support for serialization and deserialization thread-safe in lookup join
[Mixed][Improvement]:Support for serialization and deserialization thread-safe in lookup JOIN
Jan 8, 2024
Search before asking
What would you like to be improved?
Serialize and deserialize operations are not thread-safe in the
BinaryRowDataSerializerWrapper
.Using the
reuseRow
andreuseWriter
to serialize the RowData could speed the serialization process up, but it may lead to serializing incorrectly in multi-threads.Related logs:
How should we improve?
ThreadLocal provides an easy-to-use API to confine some values to each thread. This is a reasonable way of achieving thread safety in Java.
Are you willing to submit PR?
Subtasks
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: