Refactor compressors/decompressors for laziness + safety #445
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #396.
As noted in the originally reported issue, enabling debug logging when writing arrow data with compression can result in segfaults because the underlying CodecX package have debug logs, causing task switches/migration and thus making the pattern of using a single
X_COMPRESSORarray indexed byThreads.threadid()unsafe since multiple threads may try using the same compressor at the same time.We fix this by wrapping each compressor in a
Lockableand ensuring thecompress(oruncompress) operation holds the lock for the duration of the operation. We also:Successor to #397; I've added @svilupp as a co-author here since they started the original movement for the code to go in this direction.