community: fix azure cosmosdb no sql #29693
Open
Conversation
This file contains 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
dosubot
bot
added
the
size:XS
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
dosubot
bot
added
community
dosubot
bot
added
size:L
Fixes error when using custom field names Adds possibility to customize metadata.
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.
Fixes error when using custom field names
Custom fields are already aliased in the sql query, so they are no longer present in the response item. Reference the fields by the aliases.
Adds posibility to customize metadata fields.
Currently it only works if the collection has a single key with an object containing all metadata.
This adds more alternatives:
metadata_key: Field(s) to use for metadata. It can be:
- "*": all fields in the document will go in metadata.
- a string: field in the document that contains the metadata.
It must be of
objectdata type (compatible with current behavior)(it's properties will go in metadata).
- a list of strings: fields in the document to add to metadata.
Use this if metadata is spread across multiple fields.
- a dictionary: same as list but allows to alias.
A mapping of fields in the document to aliases to add as metadata
(e.g., {"field1": "alias1", "field2": "alias2"}).
- None: no metadata will be added.