From 75a430d431d1e9ba4ff6b27aac4094acb03128f2 Mon Sep 17 00:00:00 2001 From: Peter-Josef Meisch Date: Tue, 19 May 2020 19:36:35 +0200 Subject: [PATCH] DATAES-833 - Documentation fix for custom date formats. Original PR: #461 --- src/main/asciidoc/reference/elasticsearch-object-mapping.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/main/asciidoc/reference/elasticsearch-object-mapping.adoc b/src/main/asciidoc/reference/elasticsearch-object-mapping.adoc index 7e7496e7..fe1a90bd 100644 --- a/src/main/asciidoc/reference/elasticsearch-object-mapping.adoc +++ b/src/main/asciidoc/reference/elasticsearch-object-mapping.adoc @@ -48,6 +48,8 @@ The following annotations are available: ** `analyzer`, `searchAnalyzer`, `normalizer` for specifying custom custom analyzers and normalizer. * `@GeoPoint`: marks a field as _geo_point_ datatype. Can be omitted if the field is an instance of the `GeoPoint` class. +NOTE: If you are using a custom date format, you need to use _uuuu_ for the year instead of _yyyy_. This is due to a https://www.elastic.co/guide/en/elasticsearch/reference/current/migrate-to-java-time.html#java-time-migration-incompatible-date-formats[change in Elasticsearch 7]. + The mapping metadata infrastructure is defined in a separate spring-data-commons project that is technology agnostic. [[elasticsearch.mapping.meta-model.rules]]