Clinton Gormley
f0fda74083
Moved a breaking change to the correct section. Closes #14510
2015-11-08 21:53:56 +01:00
Clinton Gormley
28015d9e03
Docs: Made the list of breaking changes in each version more obvious
2015-11-08 12:59:07 +01:00
Sarwar Bhuiyan
460c74f584
changed ben to been
2015-10-12 14:39:55 +01:00
Andreas Kohn
a119e82ed0
Fix minor typo
2015-10-08 11:47:55 +02:00
Clinton Gormley
2c20658204
Docs: Added deprecation notice for _timestamp and _ttl
2015-09-07 21:16:19 +02:00
Clinton Gormley
0331e444e6
Update mapping.asciidoc
...
Added fielddata format removal to breaking changes docs
2015-08-28 18:12:54 +02:00
Clinton Gormley
a46368310a
Update mapping.asciidoc
...
Add type name length restriction to breaking changes docs.
2015-08-28 17:52:55 +02:00
xuzha
fb2be6d6a1
The name "position_offset_gap" is confusing because Lucene has three
...
similar sounding things:
* Analyzer#getPositionIncrementGap
* Analyzer#getOffsetGap
* IndexOptions.DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS and
* FieldType#storeTermVectorOffsets
Rename position_offset_gap to position_increment_gap
closes #13056
2015-08-26 14:56:35 -07:00
Nik Everett
3f6108ab74
[Mapping] Move position_offset_gap default change
...
Until a couple of hours ago we expected the position_offset_gap to default
to 0 in 2.0 and 100 in 2.1. We decided it was worth backporting that new
default to 2.0. So now that its backported we need to teach 2.1 that 2.0
also defaults to 100.
Closes #7268
2015-08-25 18:01:10 -04:00
Clinton Gormley
db1e83884f
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 20:26:18 +02:00
