fix: Use a SandboxedPersistentQueryMetadata to not interact with KafkStreams #6066
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
RequestValidator
validates every request made to KSQL using sandboxed classes that prevents modifying real data or metadata, such as creating/deleting topics, schema, etc. Even the queries running in the system are copied to prevent they're deleted during theTERMINATE
validation. However, the internalKafkaStreams
of the copied QueryMetadata is altered. The streams is closed which includes closing the originalKafkaStreams
.This PR sandboxes the
PersistentQueryMetadata
to prevent terminating theKafkaStreams
during the request validation process.Testing done
Added unit tests.
Reviewer checklist