[COST-5035] - Use json_query for OCP on GCP sql tag matching #5111
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.
Jira Ticket
COST-5035
Description
This change will tweak our special case tag matching during OCP on GCP trino SQL to avoid false positives on generic string matching.
Testing
Manually run some trino sql:
tags | namespace | match
-------------------------------------------------------------------------------------------------------+-----------+-------
{"environment":"test","namespace":"fake-namespace"} | test | true
The above (OLD method) will match fine
Whereas the below (New) method fails to match (expected)
SELECT gcp.tags, ocp.namespace, (json_query(gcp.tags, 'strict $.namespace' OMIT QUOTES) = ocp.namespace) AS match FROM gcp_tag_test AS gcp CROSS JOIN ocp_name_test AS ocp;
{"environment":"test","namespace":"fake-namespace"} | test | false
You could also test a correct match by inserting the following:
insert into ocp_name_test (namespace) values ('fake-namespace');
Then run the above sql again
Release Notes