docs(specs): Review OpenAPI Search API (index operations) #1696
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧭 What and Why
This is one of several PRs addressing the Search API.
This PR reviews just the index operations of the Search API.
Questions and notes
operationIndex
listIndices
page
parameter requires ahitsPerPage
parameter to make any sense/return sensible results. This was missing in the original OAS, I’ve added it but is the default of 100 correct?getSettings
In the response,
allowCompressionOfIntegerArray
notes say “Iftrue
, the engine applies a better compression ratio. This is recommended for arrays containing non-negative integers. When enabled, the compressed arrays may be reordered.”What’s the user benefit in compressing arrays? Is there any performance impact?
In the final sentence does this mean that the engine might reorder the array? Could this pose issues?
In the response, what's the difference between
facetOrdering
andfacets
?🎟 JIRA Ticket: DOC-1107
Changes included:
Changes to summary, description and examples
🧪 Test