Alexander Reelsen 01e8eaf181 Date Parsing: Add parsing for epoch and epoch in milliseconds ... This commit changes the date handling. First and foremost Elasticsearch does not try to convert every date to a unix timestamp first and then uses the configured date. This now allows for dates like `2015121212` to be parsed correctly. Instead it is now explicit by adding a `epoch_second` and `epoch_millis` date format. This also means, that the default date format now is `epoch_millis||dateOptionalTime` to remain backwards compatible. Closes #5328 Relates #10971		2015-06-03 18:07:47 +02:00
..
fields	Date Parsing: Add parsing for epoch and epoch in milliseconds	2015-06-03 18:07:47 +02:00
types	Date Parsing: Add parsing for epoch and epoch in milliseconds	2015-06-03 18:07:47 +02:00
date-format.asciidoc	Date Parsing: Add parsing for epoch and epoch in milliseconds	2015-06-03 18:07:47 +02:00
dynamic-mapping.asciidoc	Mappings: Remove file based default mappings	2015-04-30 13:50:35 -07:00
fields.asciidoc	Mappings: Remove _analyzer	2015-01-26 09:14:17 -08:00
meta.asciidoc	Migrated documentation into the main repo	2013-08-29 01:24:34 +02:00
transform.asciidoc	Scripting: Unify script and template requests across codebase	2015-05-29 16:52:04 +01:00
types.asciidoc	Replaced the multi-field type in favour for the multi fields option that can be set on any core field.	2014-01-13 09:21:53 +01:00