b2d82d7e75
[DOCS] Reorganised the highlight_query docs and added a version flag
2013-10-18 18:03:31 +02:00
60550e4cc2
phrase_len is not called phrase_length
2013-10-18 09:29:53 -04:00
1d0841e2b8
Added initial documentation for the redesigned percolator.
2013-10-16 14:12:19 +02:00
9a062e465c
[DOCS] Reorganised common API conventions
2013-10-13 16:46:56 +02:00
ba1b4886e3
[DOCS] Moved "named filters/queries" up one level
2013-10-10 11:23:08 +02:00
264a00a40f
[DOCS] Added pages explaining lucene query parser syntax and regular expression syntax
2013-10-07 14:42:49 +02:00
7a53d41446
[DOCS] Changed capitalization of operator in rescore query
2013-10-05 17:18:15 +02:00
f3c6108b71
introduced support for "shard_size" for terms & terms_stats facets. The "shard_size" is the number of term entries each shard will send back to the coordinating node. "shard_size" > "size" will increase the accuracy (both in terms of the counts associated with each term and the terms that will actually be returned the user) - of course, the higher "shard_size" is, the more expensive the processing becomes as bigger queues are maintained on a shard level and larger lists are streamed back from the shards.
...
closes #3821
2013-10-02 22:02:00 +02:00
6b000d8c6d
Support specifing score query on highlight.
...
This is useful if you want to highlight terms not in the search query or
you want sort highlighted snippets based on another query.
Closes #3630
2013-10-02 15:46:24 -04:00
ba40aa374e
Uniquify anchor links to fix asciidoc/docbook generation
2013-09-30 15:32:00 -06:00
0442b737be
Add more anchor links to documentation
...
Related to #3679
2013-09-30 13:13:16 -06:00
90524d7ad2
Fix formatting of the documentation.
...
Remaining '@'s have been replaced with '`'s.
2013-09-18 12:35:44 +02:00
1e3ffa0df7
Add distance supported units
2013-09-17 14:21:45 +02:00
85bba668f7
[DOCS] Tidied up various doc formatting errors
2013-09-16 16:13:01 +02:00
f6f4b5014f
Added docs for named queries.
...
Relates to #3581
2013-09-16 11:17:01 +02:00
169cd007b5
Fix typo
...
Thanks to @ybonnel for finding it ;-)
2013-09-12 11:00:59 +02:00
8ddb809f98
If all scroll ids should be removed then the `_all` value should be used instead of not specifying any scroll ids.
2013-09-12 10:41:38 +02:00
0efa78710b
Added clear scroll api.
...
The clear scroll api allows clear all resources associated with a `scroll_id` by deleting the `scroll_id` and its associated SearchContext.
Closes #3657
2013-09-10 21:17:34 +02:00
6d667e5d41
[DOCS] Missing sort values now works for all field types
2013-09-04 23:20:55 +02:00
e1c6f45ff0
[DOCS] Added clarification about global scope in facets
2013-09-04 23:20:55 +02:00
08f8e77b8f
[DOCS] Added fuzzy options to completion suggester
2013-09-04 23:20:55 +02:00
9f5d0b6e89
[DOCS] Added a few clarifications to the docs from the issues list
2013-09-04 23:20:55 +02:00
5b60506b2e
[DOCS] Added highlighting to the phrase suggester
2013-09-04 23:20:54 +02:00
53ad7330fc
[DOCS] Added docs for term vectors
2013-09-04 23:20:54 +02:00
393c28bee4
[DOCS] Removed outdated new/deprecated version notices
2013-09-03 21:28:31 +02:00
eb2fed85f1
Add 'min_input_len' to completion suggester
...
Restrict the size of the input length to a reasonable size otherwise very
long strings can cause StackOverflowExceptions deep down in lucene land.
Yet, this is simply a saftly limit set to `50` UTF-16 codepoints by default.
This limit is only present at index time and not at query time. If prefix
completions > 50 UTF-16 codepoints are expected / desired this limit should be raised.
Critical string sizes are beyone the 1k UTF-16 Codepoints limit.
Closes #3596
2013-09-03 10:26:37 +02:00
822043347e
Migrated documentation into the main repo
2013-08-29 01:24:34 +02:00
Clinton Gormley
Nik Everett
Martijn van Groningen
uboness
Lee Hinman
Adrien Grand
David Pilato
Simon Willnauer