Skip to content

Commit 5e8b569

Browse files
committed
fix highlighting docs
1 parent dc5aa99 commit 5e8b569

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

docs/reference/search/request/highlighting.asciidoc

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,6 @@ This highlighter breaks the text into sentences and scores individual sentences
5353
if they were documents in this corpus, using the BM25 algorithm.
5454
It also supports accurate phrase and multi-term (fuzzy, prefix, regex) highlighting.
5555

56-
[float]
5756
===== Offsets Strategy
5857

5958
In order to create meaningful search snippets from the terms being queried,
@@ -65,15 +64,13 @@ These offsets can be obtained from:
6564
* Term vectors (fields mapped as "term_vectors": "with_positions_offsets").
6665
* The original field, by reanalysing the text on-the-fly.
6766

68-
[float]
6967
====== Plain highlighting
7068

7169
This mode is picked when there is no other alternative.
7270
It creates a tiny in-memory index and re-runs the original query criteria through
7371
Lucene's query execution planner to get access to low-level match information on the current document.
7472
This is repeated for every field and every document that needs highlighting.
7573

76-
[float]
7774
====== Postings
7875

7976
If `index_options` is set to `offsets` in the mapping the `unified` highlighter
@@ -105,7 +102,6 @@ PUT /example
105102
--------------------------------------------------
106103
// CONSOLE
107104

108-
[float]
109105
====== Term Vectors
110106

111107
If `term_vector` information is provided by setting `term_vector` to

0 commit comments

Comments
 (0)