6 Commits

Author	SHA1	Message	Date
Neil Rickards	5189bd14f1	[Docs] Fix typo in pattern-tokenizer.asciidoc (#25626)	2017-07-13 18:43:48 +02:00
Clinton Gormley	2f6d0119f1	Added warning messages about the dangers of pathological regexes to: ... * pattern-replace charfilter * pattern-capture and pattern-replace token filters * pattern tokenizer * pattern analyzer Relates to #20038	2016-09-09 09:53:07 +02:00
Nik Everett	7aeea764ba	Remove wait_for_status=yellow from the docs ... It is no longer required after 687e2e12b3.	2016-07-15 16:02:07 -04:00
Clinton Gormley	5da9e5dcbc	Docs: Improved tokenizer docs (#18356) ... * Docs: Improved tokenizer docs Added descriptions and runnable examples * Addressed Nik's comments * Added TESTRESPONSEs for all tokenizer examples * Added TESTRESPONSEs for all analyzer examples too * Added docs, examples, and TESTRESPONSES for character filters * Skipping two tests: One interprets "$1" as a stack variable - same problem exists with the REST tests The other because the "took" value is always different * Fixed tests with "took" * Fixed failing tests and removed preserve_original from fingerprint analyzer	2016-05-19 19:42:23 +02:00
Mikhail Korobov	955473f475	Docs: unescape regexes in Pattern Tokenizer docs ... Currently regexes in Pattern Tokenizer docs are escaped (it seems according to Java rules). I think it is better not to escape them because JSON escaping should be automatic in client libraries, and string escaping depends on a client language used. The default pattern is `\W+`, not `\\W+`. Closes #6615	2014-07-03 13:34:13 +02:00
Clinton Gormley	822043347e	Migrated documentation into the main repo	2013-08-29 01:24:34 +02:00