Currently, computed columns are only supported with basic `mapper.get()` operations. They are not filled in by accessors, because user-provided queries won't necessarily have the column aliases required for computed fields to work.
We should provide a way to support computed fields with @Query. For example, the user could provide the target entity class and only the WHERE clause of the CQL query, and the driver would rebuild the full request.
Environment
None
Pull Requests
None
Activity
Alex Dutra
June 21, 2020 at 5:32 PM
This ticket has been closed on 2020-06-21 due to prolonged inactivity, as part of an automatic housekeeping procedure.
If you think that this was inappropriate, feel free to re-open the ticket. If possible, please provide any context that could explain why the issue described in this ticket is still relevant.
Also, please note that enhancements and feature requests cannot be accepted anymore for legacy driver versions (OSS 1.x, 2.x, 3.x and DSE 1.x).
Major
Currently, computed columns are only supported with basic `mapper.get()` operations. They are not filled in by accessors, because user-provided queries won't necessarily have the column aliases required for computed fields to work.
We should provide a way to support computed fields with
@Query. For example, the user could provide the target entity class and only theWHEREclause of the CQL query, and the driver would rebuild the full request.