fix: Pull Queries: Avoids inefficient KsqlConfig copy with overrides #7193
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.
Description
The call to
sessionConfig.getConfig(true);
copies fields of ksqlconfig in order to apply overrides. This is very inefficient, slowing pull query performance locally on my Mac from 10k qps for key lookups to 6k, a 40% reduction.I had made this change recently with #7006 so that the interpreter override would be available for pull queries. It had this unfortunate effect. The solution is to avoid the large copy and check overrides deliberately. We already have a pattern for this in
PullQueryConfigPlannerOptions
.Testing done
Ran unit tests
Reviewer checklist