Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Explicitly set section IDs for Asciidoctor migration #41550

Merged
merged 1 commit into from
Apr 25, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/reference/search/profile.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,7 @@ a `query` array and a `collector` array. In the future, more sections may be ad

There will also be a `rewrite` metric showing the total time spent rewriting the query (in nanoseconds).

[[_literal_query_literal_section]]
=== `query` Section

The `query` section contains detailed timing of the query tree executed by Lucene on a particular shard.
Expand Down Expand Up @@ -302,7 +303,7 @@ The meaning of the stats are as follows:

This records the time taken to score a particular document via it's Scorer


[[_literal_collectors_literal_section]]
=== `collectors` Section

The Collectors portion of the response shows high-level execution details. Lucene works by defining a "Collector"
Expand Down Expand Up @@ -378,7 +379,7 @@ For reference, the various collector reason's are:
match_all query (which you will see added to the Query section) to collect your entire dataset



[[_literal_rewrite_literal_section]]
=== `rewrite` Section

All queries in Lucene undergo a "rewriting" process. A query (and its sub-queries) may be rewritten one or
Expand Down