562 Commits

Author	SHA1	Message	Date
David Pilato	169cd007b5	Fix typo ... Thanks to @ybonnel for finding it ;-)	2013-09-12 11:00:59 +02:00
Martijn van Groningen	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
Martijn van Groningen	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
Clinton Gormley	6d667e5d41	[DOCS] Missing sort values now works for all field types	2013-09-04 23:20:55 +02:00
Clinton Gormley	e1c6f45ff0	[DOCS] Added clarification about global scope in facets	2013-09-04 23:20:55 +02:00
Clinton Gormley	08f8e77b8f	[DOCS] Added fuzzy options to completion suggester	2013-09-04 23:20:55 +02:00
Clinton Gormley	9f5d0b6e89	[DOCS] Added a few clarifications to the docs from the issues list	2013-09-04 23:20:55 +02:00
Clinton Gormley	5b60506b2e	[DOCS] Added highlighting to the phrase suggester	2013-09-04 23:20:54 +02:00
Clinton Gormley	53ad7330fc	[DOCS] Added docs for term vectors	2013-09-04 23:20:54 +02:00
Clinton Gormley	393c28bee4	[DOCS] Removed outdated new/deprecated version notices	2013-09-03 21:28:31 +02:00
Simon Willnauer	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
Clinton Gormley	822043347e	Migrated documentation into the main repo	2013-08-29 01:24:34 +02:00