Skip to content

[DOCS] Fix Bad Links in Java High-Level Search API Docs for Asciidoctor Migration #41505

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 24, 2019
Merged

[DOCS] Fix Bad Links in Java High-Level Search API Docs for Asciidoctor Migration #41505

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/java-rest/high-level/search/search.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -431,7 +431,7 @@ include-tagged::{doc-tests-file}[{api}-request-profiling-queries-results]
<4> Retrieve the profile results for the sub-queries (if any)

The Rest API documentation contains more information about {ref}/_profiling_queries.html[Profiling Queries] with
a description of the {ref}/_profiling_queries.html#_literal_query_literal_section[query profiling information]
a description of the {ref}/_profiling_queries.html#profile-query-section[query profiling information]

The `QueryProfileShardResult` also gives access to the profiling information for the Lucene collectors:

Expand All @@ -445,7 +445,7 @@ include-tagged::{doc-tests-file}[{api}-request-profiling-queries-collectors]
<4> Retrieve the profile results for the sub-collectors (if any)

The Rest API documentation contains more information about profiling information
{ref}/_profiling_queries.html#_literal_collectors_literal_section[for Lucene collectors].
{ref}/_profiling_queries.html#profile-collectors-section[for Lucene collectors].

In a very similar manner to the query tree execution, the `QueryProfileShardResult` objects gives access
to the detailed aggregations tree execution:
Expand Down
2 changes: 2 additions & 0 deletions docs/reference/search/profile.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,6 +221,7 @@ sufficient to see that a particular component of a query is slow, and not necess
the `advance` phase of that query is the cause, for example.
=======================================

[[profile-query-section]]
==== `query` Section

The `query` section contains detailed timing of the query tree executed by Lucene on a particular shard.
Expand Down Expand Up @@ -371,6 +372,7 @@ The meaning of the stats are as follows:
means the `nextDoc()` method was called on two different documents. This can be used to help judge
how selective queries are, by comparing counts between different query components.

[[profile-collectors-section]]
==== `collectors` Section

The Collectors portion of the response shows high-level execution details. Lucene works by defining a "Collector"
Expand Down