A call to CachingCodecRegistry.codecFor for HeapByteBuffer throws a CodecNotFoundException #1555
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.
Please forgive my lack of java proficiency, I'm not a java dev.
It seems like updating our spark job to spark 3 raised some issues with cassandra-driver for scala (see graphsense/graphsense-transformation#38 ).
After some research the error was narrowed down to the
CachingCodedRegistry
andBlobCodec
classes.In the first one, in the codecFor function, the primitiveCodec.accept function was sent a JavaType and not a Class type object, leading to the test for ByteBuffer.class.equals(javaClass) to fail which in turn lead to a
CodecNotFoundException
being thrown.In the BlobCodec class, only ByteBuffer.class.equals(javaClass) was used and it didn't test for child classes.
I think this issue may require a fix.