[release/3.1] Cosmos: Avoid using "value" as an alias #20574
Merged
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.
Fixes #20557
Description
EF generates aliases in the SQL query based on the projection properties. However "value" is a keyword in CosmosDB, so projections with a "Value" property result in invalid SQL.
Customer Impact
This is especially impactful when used with OData, as it generates this type of queries frequently and there's no workaround for the user.
How found
Reported by customer.
Test coverage
Added a test using this pattern.
Regression?
No.
Risk
Low. Fix only affects the alias used in the SQL.