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
[Go] FixedSizeBinary Marshal/Unmarshal returns error #35027
Comments
zeroshade
pushed a commit
that referenced
this issue
Apr 14, 2023
…rshal (#35028) This changes `FixedSizeBinaryBuilder`'s Unmarshal to use `base64.StdEncoding` instead of `base64.RawStdEncoding`. The previous implementation caused an error when unmarshaling from JSON previously produced by a `FixedSizeBinary` array instance. I also added a test for Marshal/Unmarshal to set the expectation that these operations should mirror one another. * Closes: #35027 Lead-authored-by: Herman Schaaf <hermanschaaf@gmail.com> Co-authored-by: Kemal Hadimli <disq@users.noreply.github.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
liujiacheng777
pushed a commit
to LoongArch-Python/arrow
that referenced
this issue
May 11, 2023
…r Unmarshal (apache#35028) This changes `FixedSizeBinaryBuilder`'s Unmarshal to use `base64.StdEncoding` instead of `base64.RawStdEncoding`. The previous implementation caused an error when unmarshaling from JSON previously produced by a `FixedSizeBinary` array instance. I also added a test for Marshal/Unmarshal to set the expectation that these operations should mirror one another. * Closes: apache#35027 Lead-authored-by: Herman Schaaf <hermanschaaf@gmail.com> Co-authored-by: Kemal Hadimli <disq@users.noreply.github.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
ArgusLi
pushed a commit
to Bit-Quill/arrow
that referenced
this issue
May 15, 2023
…r Unmarshal (apache#35028) This changes `FixedSizeBinaryBuilder`'s Unmarshal to use `base64.StdEncoding` instead of `base64.RawStdEncoding`. The previous implementation caused an error when unmarshaling from JSON previously produced by a `FixedSizeBinary` array instance. I also added a test for Marshal/Unmarshal to set the expectation that these operations should mirror one another. * Closes: apache#35027 Lead-authored-by: Herman Schaaf <hermanschaaf@gmail.com> Co-authored-by: Kemal Hadimli <disq@users.noreply.github.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
rtpsw
pushed a commit
to rtpsw/arrow
that referenced
this issue
May 16, 2023
…r Unmarshal (apache#35028) This changes `FixedSizeBinaryBuilder`'s Unmarshal to use `base64.StdEncoding` instead of `base64.RawStdEncoding`. The previous implementation caused an error when unmarshaling from JSON previously produced by a `FixedSizeBinary` array instance. I also added a test for Marshal/Unmarshal to set the expectation that these operations should mirror one another. * Closes: apache#35027 Lead-authored-by: Herman Schaaf <hermanschaaf@gmail.com> Co-authored-by: Kemal Hadimli <disq@users.noreply.github.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
When using
MarshalJSON
on aFixedSizeBinary
, I would expect that callingUnmarshalJSON
on aFixedSizeBinaryBuilder
with the produced JSON would read the original rows back into the builder. However right now these operations are not symmetrical, and an error is returned instead:This is because the
FixedSizeBinaryBuilder
is usingbase64.RawStdEncoding
while thejson.Marshal
method is usingbase64.StdEncoding
. It seems like we should change theFixedSizeBinaryBuilder
implementation to match thejson.Marshal
call and also usebase64.StdEncoding
.I will open a pull request to fix this shortly.
Component(s)
Go
The text was updated successfully, but these errors were encountered: