This repository was archived by the owner on Jun 3, 2021. It is now read-only.
Throttle Hive splits discovery #19
Open
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.
This is a work in progress to throttle the hive split discovery.
If the value of
hive.max-outstanding-splits
is greater than0
, thenHiveSplitSource
will use theThrottledAsyncQueue
to enqueue the splits, which throttles the returned batches to release at most that amount of splits per seconds to the consumer, thus throttling the split discovery mechanism for hive.Note that
hive.max-outstanding-splits
needs to be more thanquery.min-schedule-split-batch-size
otherwiseBufferingSplitSource
will buffer the throttled splits and assign them all at once, cancelling the "smoothing" effect of throttling the splits.