Update schema.rs for metadata json parsing #529
Closed
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
bug fix for issue 457, 524. This will enable to read metadata containing a numerical value For more detail, please refer delta-io#524 delta-io#457
|
duplicate of #531 |
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.
bugfix for issue 457, 524. This will enable to read metadata containing a numerical value
For more detail, please refer
#524
#457
Description
Users were facing an issue while reading delta table using delta-rs library when there was a numerical value present in the metadata column of delta transaction log. Users used to get
Failed to apply transaction log: Invalid JSON in log record errorerrorRelated Issue(s)
#524
#457
--->
Documentation
Replaced
HashMap<String, String>withHashMap<String, serde_json::Value>indelta-rs/rust/src/schema.rs
Line 57 in 57133e1