James Rodewig
4629a9714c
[DOCS] Fix time_zone example in range query docs ( #50830 )
...
One of the example snippets in the range query docs was missing a
required 'T' in the `date` format. This adds the required 'T'.
2020-01-10 08:24:48 -05:00
rikardbakkehaug
6b00e00bc6
[DOCS] Correct date math ex for `gt` and `gte` parms in `range` query docs ( #46873 )
2019-09-19 16:39:03 -04:00
James Rodewig
e253ee6ba6
[DOCS] Change // CONSOLE comments to [source,console] ( #46440 ) ( #46494 )
2019-09-09 12:35:50 -04:00
James Rodewig
4b8ae97e9d
[DOCS] Update relevance score cross-references ( #45092 )
2019-08-02 14:15:34 -04:00
James Rodewig
728b0cf9ff
[DOCS] Update parameter format ( #44703 )
2019-07-31 14:18:55 -04:00
James Rodewig
661f70183e
[DOCS] Make Query DSL titles consistent ( #43935 )
2019-07-18 10:33:10 -04:00
James Rodewig
50eac875e4
[DOCS] Rewrite `range` query ( #43282 )
2019-06-25 15:25:48 -04:00
Christoph Büscher
4f5a83dba2
Clarify using time_zone and date math in range query ( #40655 )
...
Currently, the docs correctly state that using `now` in range queries will not
be affected by the `time_zone` parameter. However, using date math roundings
like e.g. `now\d` will be affected by the `time_zone`. Adding this example
because it seems to be a frequently asked question and source of confusion.
Relates to #40581
2019-03-29 23:39:18 +01:00
Gytis Šk
3ee37b425b
Docs: Add section about range query for range type ( #35222 )
...
This makes their interaction more discoverable.
2018-11-06 10:49:12 -05:00
Christoph Büscher
3f78b3f5e1
[Docs] Explain incomplete dates in range queries ( #30689 )
...
The current documentation isn't very clear about how incomplete dates are
treated when specifying custom formats in a `range` query. This change adds a
note explaining how missing month or year coordinates translate to dates that
have the missings slots filled with unix time start date (1970-01-01)
Closes #30634
2018-05-24 11:20:00 +02:00
Isabel Drost-Fromm
4c02e97bcd
Add back doc execution to query dsl.
...
Relates to #18211
This reverts commit 20aafb1196
.
2016-05-24 12:43:41 +02:00
Isabel Drost-Fromm
20aafb1196
Revert "Add Autosense annotation for query dsl testing"
2016-05-17 20:55:56 +02:00
Isabel Drost-Fromm
ab4367c07e
Add CONSOLE to span queries.
...
... and range, and terms...
2016-05-10 12:59:44 +02:00
Isabel Drost-Fromm
a865090cf3
CONSOLE is the new AUTOSENSE
2016-05-10 12:42:17 +02:00
Isabel Drost-Fromm
e486560ea8
Add Autosense annotation for query dsl testing
...
this adds the autosense annotation to a couple of query dsl
docs files and fixes the snippets to work in the tests along
the way.
2016-05-10 11:54:48 +02:00
Rafał Bigaj
ead431f524
Duplicated colon was removed ( #17988 )
...
Hope this help :-)
2016-04-26 20:31:00 +02:00
André Carvalho
070c836dce
Gives more emphasys
2015-09-24 11:30:00 -03:00
André Carvalho
d90fc8f7fd
Documents that now is not affected by time_zone in range queries
2015-09-23 22:00:49 -03:00
Clinton Gormley
ac2b8951c6
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 17:24:51 +02:00
Ryan Ernst
dba42a83e2
Docs: Update time_zone specification
...
closes #12317
2015-07-21 00:22:53 -07:00
Clinton Gormley
171687d207
Docs: Reorganised the Query DSL docs into families and explaing query vs filter context
2015-06-04 01:59:37 +02:00
Adrien Grand
a0af88e996
Query DSL: Remove filter parsers.
...
This commit makes queries and filters parsed the same way using the
QueryParser abstraction. This allowed to remove duplicate code that we had
for similar queries/filters such as `range`, `prefix` or `term`.
2015-05-07 20:14:34 +02:00