-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add raw MapArrayReader #3703
Add raw MapArrayReader #3703
Conversation
@@ -100,7 +93,7 @@ impl<O: OffsetSizeTrait> ArrayDecoder for ListArrayDecoder<O> { | |||
offsets.append(offset) | |||
} | |||
|
|||
let child_data = self.decoder.decode(tape, &child_pos).unwrap(); | |||
let child_data = self.decoder.decode(tape, &child_pos)?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drive by fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
assert_eq!(map.value_offsets(), &[0, 1, 3, 5]); | ||
|
||
let k: Vec<_> = map_keys.iter().map(|x| x.unwrap()).collect(); | ||
assert_eq!(&k, &["a", "a", "b", "c", "a"]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
arrow-json/src/raw/mod.rs
Outdated
assert_eq!(&lv, &[Some("foo"), None, None, Some("baz")]); | ||
assert_eq!(map_values.value_offsets(), &[0, 2, 3, 3, 3, 4]); | ||
assert_eq!(map_values.null_count(), 1); | ||
assert!(map_values.is_null(3)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we can use our fancy new arrow display writer here to write out the contents of the arrays as well 🤔
Benchmark runs are scheduled for baseline = ef00365 and contender = 7083f12. 7083f12 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Part of #3610
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?