Closed akshaysu closed 1 year ago
It is unfortunate to have the name
within the column name comparison, but we always considered the column name as comparison argument. This issue is a bug at its core because we should not sort by column name but rather fall back to the field order.
For the time being, please use @PrimaryKeyColumn(ordinal = …)
to provide a sort order for your columns.
I found that when having composite key in the entity, generated DDL differs when @PrimaryKeyColumn.name is used. spring-data-cassandra version - 4.0.4 java-driver-core - 4.15.0 cassandra server - 4.0.8
Example:
Generated DDL is
Generated DDL is
It seems issue is not using class field name as column name while ordering the properties of the primary key class Entity. Please confirm whether this is an issue.
Thanks