Hotfix for CosmosDb_NoSql filtering issue on March Release#1448
Merged
tarazou9 merged 5 commits intorelease/Mar2023from Apr 25, 2023
Merged
Hotfix for CosmosDb_NoSql filtering issue on March Release#1448tarazou9 merged 5 commits intorelease/Mar2023from
tarazou9 merged 5 commits intorelease/Mar2023from
Conversation
seantleonard
approved these changes
Apr 24, 2023
Contributor
|
Can you update the PR description please? |
Aniruddh25
approved these changes
Apr 24, 2023
Collaborator
Aniruddh25
left a comment
There was a problem hiding this comment.
Thanks for the hot patch! LGTM, after fixing the description.
Contributor
Author
Updated, thank you for pointing this out! |
seantleonard
requested changes
Apr 25, 2023
seantleonard
approved these changes
Apr 25, 2023
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
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.
Why make this change?
operationToColumnMap.ExcludedandoperationToColumnMap.Includedand by introducing field level auth check into theGQLFilterParserrecent update results the issue that we are seeing.CosmosMetadataProviderdoes not translate a field wild card (*) or list of hardcoded include columns to the list of AllowedFields in the engine'sAuthorizationResolvercurrently, but we can add a pass through to theTryGetExposedColumnNameas suggested so it doesn't throw aNotImplementedExceptionwhen user accidently passed in the fields settings in the Cosmos configuration file.What is this change?
How was this tested?
Sample Request(s)