Closed usuket closed 2 years ago
Hi @usuket, thanks for reporting this.
The Cassandra Quarkus extension does support UDTs, but it is true that we currently do not test this in our integration tests. I added a few tests in a new PR, see #202.
As you can see there, UDT classes must be annotated with @Entity
. However your class is annotated with @UDT(name = "payment")
– but @UDT
is not a supported annotation.
My guess is that you are mixing jars from driver 4.x and 3.x in your application, because @UDT
used to be a valid annotation in driver 3.x, but not in driver 4.x.
Please remove all dependencies to driver 3.x from your code as this driver version is NOT compatible with the Cassandra Quarkus extension.
Read more about mapping features in driver 4.x here.
Let me know if that helps.
I'm going to close this to avoid stale issues. Feel free to reopen if you have further questions. Thanks!
@adutra I apologize for the late reply.
I confirmed that it works well with @Entity
annotation with the latest version of the Cassandra Driver.
Thank you for your support.
Hello,
I am building new API application with cassandra-quarkus driver with Cassandra 3.11.6
But I stacked CQL conversion due to missing codec in the codec registry. I am pretty sure the issue comes from the UDT, Codec, and Registry but I couldn't figure out a way to register the codec.
I built the basic function based on the quickstart project, and it worked without any trouble except UDT.
I tried annotation with com.datastax.driver.mapping.annotations.UDT and field:Column with Codec. I believe UDT is a common use case, can you help me or can you add additional information to the document or sample code?
These are my kotlin codes and DDL, I will put them as a reference. (But I modified the field name and package name so it might not be accurate)
Thanks in advance.
Track trace is.
┆Issue is synchronized with this Jira Task by Unito