mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 15:47:23 -04:00
Free and Open, Distributed, RESTful Search Engine
2d3bcc483d
* [DOCS] Warn only one date format is added to the field date formats
When using multiple options in `dynamic_date_formats`, only one of the formats of the first document having a date matching one of the date formats provided will be used.
E.g.
```
PUT my-index-000001
{
"mappings": {
"dynamic_date_formats": [ "yyyy/MM", "MM/dd/yyyy"]
}
}
PUT my-index-000001/_doc/1
{
"create_date": "09/25/2015"
}
```
The generated mappings will be:
```
"mappings": {
"dynamic_date_formats": [
"yyyy/MM",
"MM/dd/yyyy"
],
"properties": {
"create_date": {
"type": "date",
"format": "MM/dd/yyyy"
}
}
},
```
Indexing a document with `2015/12` would lead to the `format` `"yyyy/MM"` being used for the `create_date`.
This can be misleading especially if the user is using multiple date formats on the same field.
The first document will determine the format of the `date` field being detected.
Maybe we should provide an additional example, such as:
```
PUT my-index-000001
{
"mappings": {
"dynamic_date_formats": [ "yyyy/MM||MM/dd/yyyy"]
}
}
```
My wording is not great, so feel free to amend/edit.
* Update docs/reference/mapping/dynamic/field-mapping.asciidoc
Reword and add code example
* Turned discussion of the two syntaxes into an admonition
* Fix failing tests
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
|
||
|---|---|---|
| .ci | ||
| .github | ||
| .idea | ||
| benchmarks | ||
| build-conventions | ||
| build-tools | ||
| build-tools-internal | ||
| ccr/images | ||
| client | ||
| dev-tools | ||
| distribution | ||
| docs | ||
| gradle | ||
| libs | ||
| licenses | ||
| modules | ||
| plugins | ||
| qa | ||
| rest-api-spec | ||
| server | ||
| test | ||
| x-pack | ||
| .backportrc.json | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| build.gradle | ||
| BUILDING.md | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| README.asciidoc | ||
| REST_API_COMPATIBILITY.md | ||
| settings.gradle | ||
| TESTING.asciidoc | ||
| TRACING.md | ||
| Vagrantfile | ||
= Elasticsearch Elasticsearch is the distributed, RESTful search and analytics engine at the heart of the https://www.elastic.co/products[Elastic Stack]. You can use Elasticsearch to store, search, and manage data for: * Logs * Metrics * A search backend * Application monitoring * Endpoint security \... and more! To learn more about Elasticsearch's features and capabilities, see our https://www.elastic.co/products/elasticsearch[product page]. [[get-started]] == Get started The simplest way to set up Elasticsearch is to create a managed deployment with https://www.elastic.co/cloud/as-a-service[Elasticsearch Service on Elastic Cloud]. If you prefer to install and manage Elasticsearch yourself, you can download the latest version from https://www.elastic.co/downloads/elasticsearch[elastic.co/downloads/elasticsearch]. For more installation options, see the https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html[Elasticsearch installation documentation]. [[upgrade]] == Upgrade To upgrade from an earlier version of Elasticsearch, see the https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html[Elasticsearch upgrade documentation]. [[build-source]] == Build from source Elasticsearch uses https://gradle.org[Gradle] for its build system. To build a distribution for your local OS and print its output location upon completion, run: ---- ./gradlew localDistro ---- To build a distribution for another platform, run the related command: ---- ./gradlew :distribution:archives:linux-tar:assemble ./gradlew :distribution:archives:darwin-tar:assemble ./gradlew :distribution:archives:windows-zip:assemble ---- To build distributions for all supported platforms, run: ---- ./gradlew assemble ---- Distributions are output to `distributions/archives`. To run the test suite, see xref:TESTING.asciidoc[TESTING]. [[docs]] == Documentation For the complete Elasticsearch documentation visit https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html[elastic.co]. For information about our documentation processes, see the xref:docs/README.asciidoc[docs README]. [[contribute]] == Contribute For contribution guidelines, see xref:CONTRIBUTING.md[CONTRIBUTING]. [[questions]] == Questions? Problems? Suggestions? * To report a bug or request a feature, create a https://github.com/elastic/elasticsearch/issues/new/choose[GitHub Issue]. Please ensure someone else hasn't created an issue for the same topic. * Need help using Elasticsearch? Reach out on the https://discuss.elastic.co[Elastic Forum] or https://ela.st/slack[Slack]. A fellow community member or Elastic engineer will be happy to help you out.