-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Codec not found for requested operation using a Set
of mapped User Defined Type
#1473
Labels
type: bug
A general bug
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Feb 3, 2024
Care to provide the Table and UDT CQL definitions so we have a complete reproducer? |
mp911de
added
the
status: waiting-for-feedback
We need additional information before we can continue
label
Feb 5, 2024
Sure, I used
|
spring-projects-issues
added
status: feedback-provided
Feedback has been provided
and removed
status: waiting-for-feedback
We need additional information before we can continue
labels
Feb 6, 2024
mp911de
added
type: bug
A general bug
and removed
status: waiting-for-triage
An issue we've not yet triaged
status: feedback-provided
Feedback has been provided
labels
Feb 6, 2024
mp911de
changed the title
Codec not found for requested operation, When updating collection of UDT in custom query
Codec not found for requested operation using a Feb 6, 2024
Set
of mapped User Defined Type
mp911de
added a commit
that referenced
this issue
Feb 6, 2024
We now deeply introspect collection and map elements when obtaining write values to ensure proper UDT and tuple conversions. Previously, collections containing UDT values did a pass-thru of values instead of applying UDT mapping. Closes #1473
mp911de
added a commit
that referenced
this issue
Feb 6, 2024
We now deeply introspect collection and map elements when obtaining write values to ensure proper UDT and tuple conversions. Previously, collections containing UDT values did a pass-thru of values instead of applying UDT mapping. Closes #1473
Thanks a lot. We were missing collection introspection of elements if the element type wasn't sufficient. That's fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I have test application working with Cassandra repositories.
When I try to write a custom query and a partial update on a column which it's type is a collection of UDT, I get this error:
Here is my entity:
But if i dont put
Speciality
in a collection and update it using the same way, there is no problem.Tested with spring boot 3.2.0 and spring-data-cassandra 4.2.0
The text was updated successfully, but these errors were encountered: