Move parallel fetch config into index live settings #740
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Move the configuration options for parallel fetch out of
ThreadPoolConfigurationand into the index live settings.There are two config options:
parallelFetchByField- if the work should be divided by fields instead of by documentparallelFetchChunkSize- the maximum number of fields/documents to process in a single fetch taskEnabling parallel fetch is still based on the fetch thread pool configuration. If the max threads is > 1, fetch is enabled. The maximum number of fetch tasks per query is limited by the thread pool max threads.