Improve the performance of the Trino Rego rules #289
Merged
+267
−256
Conversation
This file contains hidden or 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
siegfriedweber
added
release-note
maltesander
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
siegfriedweber
moved this from Development: In Review
to Development: Done
in Stackable Engineering
lfrancke
moved this from Development: Done
to Acceptance: In Progress
in Stackable Engineering
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.
Improve the performance of the Trino Rego rules
see stackabletech/trino-operator#782
The new Trino rules were copied from the integration test to the end-to-end-security stack.
The end-to-end-security demo was successfully tested with the new rules.
Release notes
The performance of the Trino rules in the end-to-end-security stack was improved. Batch queries are now significantly faster.