@Property annotation disrupts aggregation mapping

Using 1.4.1

I’m getting this error when trying to aggregate, using a class to specify the aggregation results: MappingException: Error setting value from converter (IdentityConverter) for...

In the handler:

final Dao<Client> clientDao = new Dao<>(Client.class);
final Iterator<ClientAggregate> iterator = clientDao.newAggregation()
        .match(query)
        .lookup(DbCollections.PHONE_NUMBERS, Client.PRIMARY_PHONE_ID, Phone.ID, Client.PRIMARY_PHONE)
        .unwind(Client.PRIMARY_PHONE)
        .aggregate(ClientAggregate.class);

ClientAggregate.java

public class ClientAggregate extends Client {

    @Property(PRIMARY_PHONE)  // <-- causes failure
    private Phone primaryPhone;

}

I’m not sure if this is by design, but I always annotate my fields with PSFS values, so I can make any changes to the values globally instead of refactoring the actual property name.

If I remove the @Property annotation and name the field the same as the as option during the $lookup stage, it works fine. Is there a reason this fails, because it would be nice to use the annotation rather than relying on the actual field name.

[nolawnchairs]

@Embedded works as expected. Honestly never crossed my mind to use that. I’ll show myself out…

[evanchooly]

what happens if you use @Embedded there? That’s the correct annotation there…