-
Notifications
You must be signed in to change notification settings - Fork 222
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
Cannot set default value for timestamp logical types #198
Comments
I just updated the issue description with a small proof of concept. |
Thanks. That should help. |
sixstone-qq
added a commit
to heetch/hkt
that referenced
this issue
Nov 16, 2021
sixstone-qq
added a commit
to heetch/hkt
that referenced
this issue
Nov 18, 2021
sixstone-qq
added a commit
to heetch/hkt
that referenced
this issue
Nov 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The same issue as In #122
Creating a new one since got no response there. For any timestamp type with
logicalType
timestamp-millis
, setting default value0
(not a string), throws an error.In the linked ticket it seems people talk about strings being used as default for
long
timestamp.Our use case is more valid where default
0
long does not work as expected.Here is a small test to reproduce the issue.
The test fails with
Record "schema" field "timestamp": default value ought to encode using field schema: cannot transform binary timestamp-millis, expected time.Time, received float64
.The same test does not fail when import path is changed to
github.com/linkedin/goavro
.The text was updated successfully, but these errors were encountered: