{{@DateBridge}} resolution used to be supported for {{java.util.Date}} and {{java.util.Calendar}}, but not {{java.time}} types.
It’s no longer supported at all in Hibernate Search 6, because truncating a {{java.util.Date}} requires us to pick a timezone, and there’s no way to be sure that’s the timezone the user expected.
However, we could restore support for resolution in very specific cases:
* For date/time types where the timezone is not necessary in order to truncate a value (e.g. {{LocalDateTime}}, {{LocalDate}}) * For date/time types where the timezone is included in the value to truncate (e.g. {{ZonedDateTime}}, {{OffsetDateTime}}) * Optionally, for date/time types where an external timezone must be provided, in which case it could be part of the mapping ({{@TemporalField(resolution = ..., timeZone = "UTC+2")}} / {{@TemporalField(resolution = ..., timeZoneProvider = @BeanReference(name = "myBean")}}) |
|