DATACASS-206, DATACASS-308 Fix delete using custom column names and NullPointerException related properties using the MapId mechanism #73
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.
We now use the specified column name from the entity annotation to construct the where clause in a delete statement.
We also now reject unknown/misspelled property names when using
MapId. The Id conversion and extraction now takes place in the Cassandra Converter. The Id handling code inCassandraTemplateis deprecated.Also, some polishing to in that context to reorder fields in MappingCassandraConverter according to their visibility. Remove code duplicates. Improve JavaDoc in CassandraOperations. Align entity class parameter names in CassandraTemplate. Enhance JavaDoc for built statement factory methods. Add guards to method arguments.
Related tickets: DATACASS-206 and DATACASS-308.