You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/asciidoc/reference/elasticsearch-object-mapping.adoc
+5-5
Original file line number
Diff line number
Diff line change
@@ -56,10 +56,10 @@ This section details the annotations that define if the value of a property is w
56
56
57
57
`@Transient`: A property annotated with this annotation will not be written to the mapping, it's value will not be sent to Elasticsearch and when documents are returned from Elasticsearch, this property will not be set in the resulting entity.
58
58
59
-
`@ReadOnlyProperty`: A property with this annotaiton will not have its value written to Elasticsearch, but when returning data, the proeprty will be filled with the value returned in the document from Elasticsearch.
59
+
`@ReadOnlyProperty`: A property with this annotation will not have its value written to Elasticsearch, but when returning data, the property will be filled with the value returned in the document from Elasticsearch.
60
60
One use case for this are runtime fields defined in the index mapping.
61
61
62
-
`@WriteOnlyProperty`: A property with this annotaiton will have its value stored in Elasticsearch but will not be set with any value when reading document.
62
+
`@WriteOnlyProperty`: A property with this annotation will have its value stored in Elasticsearch but will not be set with any value when reading document.
63
63
This can be used for example for synthesized fields which should go into the Elasticsearch index but are not used elsewhere.
@@ -71,7 +71,7 @@ This paragraph describes the use of
71
71
72
72
There are two attributes of the `@Field` annotation that define which date format information is written to the mapping (also see https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-date-format.html#built-in-date-formats[Elasticsearch Built In Formats] and https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-date-format.html#custom-date-formats[Elasticsearch Custom Date Formats])
73
73
74
-
The `format` attributes is used to define at least one of the predefined formats.
74
+
The `format` attribute is used to define at least one of the predefined formats.
75
75
If it is not defined, then a default value of __date_optional_time_ and _epoch_millis_ is used.
76
76
77
77
The `pattern` attribute can be used to add additional custom format strings.
@@ -191,7 +191,7 @@ public String getProperty() {
191
191
192
192
This annotation can be set on a String property of an entity.
193
193
This property will not be written to the mapping, it will not be stored in Elasticsearch and its value will not be read from an Elasticsearch document.
194
-
After an entity is persisted, for example with a call to `ElasticsearchOperations.save(T entity)`, the entity
194
+
After an entity is persisted, for example with a call to `ElasticsearchOperations.save(T entity)`, the entity
195
195
returned from that call will contain the name of the index that an entity was saved to in that property.
196
196
This is useful when the index name is dynamically set by a bean, or when writing to a write alias.
197
197
@@ -438,7 +438,7 @@ public class Config extends ElasticsearchConfiguration {
438
438
439
439
@WritingConverter <2>
440
440
static class AddressToMap implements Converter<Address, Map<String, Object>> {
441
-
441
+
442
442
@Override
443
443
public Map<String, Object> convert(Address source) {
0 commit comments