Supply a custom `Sort.Order` providing Elasticsearch specific parameters

[sothawo]

Spring Data Elasticsearch should supply a Sort.Order derived class that can provide custom parameters like ignore_unmapped (see #1908) for an example where this is needed

[alan-czajkowski]

can I see an example of a Sort.Order that sets ignore_unmapped to true?

[sothawo]

for example

Sort sort = Sort.by(new GeoDistanceOrder("property", new GeoPoint(47.5, 6.4)).withIgnoreUnmapped(false));

[alan-czajkowski]

@sothawo I'm trying to sort on a Java Date field (which appears to map to a long type), how would I do it?

[sothawo]

ignore_unmapped is only available for geo sorts (https://www.elastic.co/guide/en/elasticsearch/reference/8.1/sort-search-results.html#geo-sorting)

If a Date (please don't use java.utile.Date but the classes from the java.time package) is mapped to a long depends on how you define the mapping. You can set the unmapped type and the missing behaviour on Order

[alan-czajkowski]

@sothawo this is a Spring Data Elasticsearch problem, how do I achieve this with Sort/Sort.Order ?

[alan-czajkowski]

@sothawo is there some way to set unmapped_type using Spring Data ES annotation?
should this be a feature request for the org.springframework.data.elasticsearch.annotations.Setting annotation?

for a field like:
private LocalDateTime created;

it would be nice for Spring Data ES to translate something down into this ES code:
SortOrder sortOrder = SortBuilders.fieldSort("created").unmappedType("long").order();

[alan-czajkowski]

@sothawo I've also noticed that you have mentioned many times online to switch from java.util.Date to java.time.* but when I converted all of my java.util.Date instances to java.time.LocalDateTime I now get this error:
with Spring 5.3 and Spring Data ES 4.3

org.springframework.core.convert.ConverterNotFoundException: No converter found capable of converting from type [java.lang.Long] to type [java.time.LocalDateTime]

all of my java.util.Date instances worked natively with Spring Data ES, I did not have to define any explicit annotations on my date fields or implement any converters, but now none of my @Document entities work because of this new exception

[sothawo]

it would be nice for Spring Data ES to translate something down into this ES code:
SortOrder sortOrder = SortBuilders.fieldSort("created").unmappedType("long").order();

that was exactly the point of this issue. So now it is possible to do

import org.springframework.data.elasticsearch.core.query.Order;

Sort sort = Sort.by(new Order(Sort.Direction.ASC, "created").withUnmappedType("long"));

and use that sort in a Pageable as parameter or whatever.

How is this date field mapped in your index? Is it really unmapped? What does /<indexname>/_mappings show for that property? If you have data for that property in the index then it will be surely mapped, so adding an unmapped type to a sort has not effect. What is the problem that you have with the sorting?

As for the temporal types: java.util.Date is an instance in time in UTC time zone. A LocalDateTime does not have a timezone, so it cannot be instantiated from a long. The appropriate data type would be java.time.Instant