Fix for the Prepared IN Clause giving java.lang.ClassCastException error For 4.15.x #36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem:
Getting the “error java.lang.ClassCastException: java.util.ArrayList cannot be cast to com.datastax.oss.driver.api.core.type.SetType” when IN Clause contains list as the bound variable. More details here.
Reason:
The issue was because the list types and set types were handled similarly in the 4.x driver where the Datatype was explicitly converted to Set type. In the 4.x driver, DataType is an interface, which different datatypes implement.
The issue did not come on the 3.x driver because there was no explicit type conversion, since datatype is not an interface in the 3.x driver but a class that handles all the data types.
Solution:
Added a different implementation for list type