17 Commits

Author SHA1 Message Date
Adrien Grand
1b660821a2
Allow _doc as a type. ()
Allowing `_doc` as a type will enable users to make the transition to 7.0
smoother since the index APIs will be `PUT index/_doc/id` and `POST index/_doc`.
This also moves most of the documentation to `_doc` as a type name.

Closes 
Closes 
2017-12-14 17:47:53 +01:00
Christoph Büscher
0d11b9fe34
[Docs] Unify spelling of Elasticsearch ()
Removes occurences of "elasticsearch" or "ElasticSearch" in favour of
"Elasticsearch" where appropriate.
2017-11-29 09:44:25 +01:00
shaulzorea
9db21cd23f fixing typo in datehistogram-aggregation.asciidoc () 2017-10-08 15:12:43 +02:00
Nik Everett
7e76b2a8c3 Docs: fold section into current chapter
In  we added a new *chapter* on aggregating by day of the
week. We intended to add a new *section* but we were missing a
single `=`.
2017-08-17 11:19:02 -04:00
matarrese
2eafbaf759 Document aggregating by day of the week ()
Add documentation for aggregating by day of the week.

Closes 
2017-07-07 14:16:53 -04:00
qwerty4030
e7d352b489 Compound order for histogram aggregations. ()
This commit adds support for histogram and date_histogram agg compound order by refactoring and reusing terms agg order code. The major change is that the Terms.Order and Histogram.Order classes have been replaced/refactored into a new class BucketOrder. This is a breaking change for the Java Transport API. For backward compatibility with previous ES versions the (date)histogram compound order will use the first order. Also the _term and _time aggregation order keys have been deprecated; replaced by _key.

Relates to : now that all these aggregations use the same order code, it should be easier to move validation to parse time (as a follow up PR).

Relates to : histogram and date_histogram aggregation order will now be validated at reduce time.

Closes : if a single BucketOrder that is not a tie-breaker is added with the Java Transport API, it will be converted into a CompoundOrder with a tie-breaker.
2017-05-11 18:06:26 +01:00
Suhas Karanth
cee76295ca Update aggs reference documentation for 'keyed' options ()
Add 'keyed' parameter documentation for following:
 - Date Histogram Aggregation
 - Date Range Aggregation
 - Geo Distance Aggregation
 - Histogram Aggregation
 - IP range aggregation
 - Percentiles Aggregation
 - Percentile Ranks Aggregation
2017-04-18 15:57:50 +02:00
Jun Ohtani
94933f9d19 [Doc]Not support "M" time unit in offset param 2017-01-31 18:23:38 +09:00
Nik Everett
f7524fbdef CONSOLE-ify date histogram docs
This adds the `VIEW IN SENSE` and `COPY AS CURL` links and has
the build automatically execute the snippets and verify that they
work.

Relates to 
2017-01-20 16:23:28 -05:00
Christoph Büscher
4ccd8e79c1 Docs: Clarify date_histogram bucket sizes for DST time zones
Added a warning note that clarifies bucket sizes diverging from the intended
`interval` size when using a time zone that has DST changes.

Closes 
2016-11-16 09:40:07 +01:00
Jason Tedor
00356edd33 Clarify time units usage in docs
This commit clarifies the distinction between supported time units for
durations and supported time units for durations in the docs.

Relates 
2016-06-29 17:02:15 -04:00
Kevin Adams
768d171f77 Timezone: use forward slash
Using a backslash causes errors when querying elasticsearch, but changing the back slash to forward slash on the timezone fixes it.

Closes 
2016-01-22 14:26:49 +01:00
Alex
4077a322c5 Docs: Fix typo - datehistogram
date_histogram in place of datehistogram

Closes 
2015-10-06 19:22:21 +02:00
Clinton Gormley
8aba6ce93a Docs: Improved the date histogram docs for time_zone and offset 2015-09-07 19:54:00 +02:00
Ryan Ernst
dba42a83e2 Docs: Update time_zone specification
closes 
2015-07-21 00:22:53 -07:00
Adrien Grand
32e23b9100 Aggs: Make it possible to configure missing values.
Most aggregations (terms, histogram, stats, percentiles, geohash-grid) now
support a new `missing` option which defines the value to consider when a
field does not have a value. This can be handy if you eg. want a terms
aggregation to handle the same way documents that have "N/A" or no value
for a `tag` field.

This works in a very similar way to the `missing` option on the `sort`
element.

One known issue is that this option sometimes cannot make the right decision
in the unmapped case: it needs to replace all values with the `missing` value
but might not know what kind of values source should be produced (numerics,
strings, geo points?). For this reason, we might want to add an `unmapped_type`
option in the future like we did for sorting.

Related to 
2015-05-15 16:26:58 +02:00
Zachary Tong
e3ae1df6f0 [DOCS] Restructure Aggs documentation 2015-05-01 16:04:55 -04:00