Breaking change from `4.2.7-SNAPSHOT` to `4.3.1` for repositories with abstract or interface entities

This repository method causes an issue with 4.3.1 but not with 4.2.7-SNAPSHOT :

@Query("#{#n1ql.selectEntity} USE KEYS $1")
List<BaseManageableEntity> findAllByIdIn(List<String> ids);

This method can return a variety of types of documents all extending the BaseManageableEntity abstract class. With 4.2.7-SNAPSHOT the returned objects have the type of their inner class, A or B both extending BaseManageableEntity, the list carries the lower bound and is of type List<BaseManageableEntity>. With 4.3.1 the returned method tries to deserialize the documents as instances of BaseManageableEntity causing an error, since BaseManageableEntity is an abstract class.

The behavior of 4.2.7-SNAPSHOT is the correct behavior imo, since it’s easier and more natural to go in this direction than the other one.

[mikereiche]

btw - derived queries (those without an @Query definition) on a repository for an abstract entity class and the default type (i.e. no @TypeAlias) will never select any rows that have been saved by that repository because the _class = <entity-class-name> predicate will use the abstract class name, while the documents will have been saved with their concrete class name.

[mikereiche]

February 18. https://calendar.spring.io/ (2021.1.x -> 4.3.x) I’ve updated 4.3x just now, the next 4.3.2-SNAPSHOT will have the change.