@Field name not used for repository method

[JesusTheHun]

Still migrating our app to Spring Data Couchbase 4, we have the following situation :

@Document
@Data
public class Foo extends AbstractAuditingEntity<Foo> implements Serializable {
    @Field("some_prop")
    private String someProp;
}

@Repository
public interface FooRepository extends CouchbaseRepository<Foo, String> {
    List<Foo> findBySomeProp(String someProp);
}

When I call fooRepository.findBySomeProp(...) the result is an empty entity except for the id and the audit fields.
I dug down and I found out that ReactiveFindByQueryOperationSupport.all(...) assembled query is :

SELECT META(`acme`).id AS __id, META(`acme`).cas AS __cas, `prefix`, `someProp`, `revision`, `createdById`, `createdDate`, `lastModifiedById`, `lastModifiedDate` FROM `acme` WHERE `_class` = "acme.domain.Foo" AND `some_prop` = $1

As you can see the field is correct in the WHERE clause but not in the SELECT.
Therefore the returned object is mostly empty, all business properties are null.

Did we forget to configure something ? Native methods works well.

[mikereiche]

That's a bug that has been fixed - but maybe only in 4.3.0-M3. What version do you have? I'll investigate later today.

[mikereiche]

This is #1184 . The corresponding PR (1185) just adds a test. The actual fix is in a rather large change ( 4bd82ea )

[mikereiche]

I've back-ported the fix and test case to 4.2.x . It will be in 4.2.6 release scheduled for October 14.

[JesusTheHun]

Thank you for the backport !
We currently use 4.2.6-SNAPSHOT to use the previous consistency fix you submitted. We will pin the version once the migration is over, so it will probably be 4.2.6, we'll push for the 4.3.0 as apparently there are numerous fixes in it.