-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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] TimestampType zero value default to seconds unit instead of nanoseconds #35770
Labels
Milestone
Comments
@ddl-gabrielhaim good catch. A bunch of the math and shortcuts are based on the fact that the enum value of |
zeroshade
pushed a commit
that referenced
this issue
Sep 27, 2023
…nds in comment (#37905) ### Rationale for this change To clear the confusion around the zero value of `TimestampType` ### What changes are included in this PR? Just a comment change `nanosecond -> second` ### Are these changes tested? No need to test ### Are there any user-facing changes? No Closes: #35770 * Closes: #35770 Authored-by: ismail simsek <ismailsimsek09@gmail.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
etseidl
pushed a commit
to etseidl/arrow
that referenced
this issue
Sep 28, 2023
…s seconds in comment (apache#37905) ### Rationale for this change To clear the confusion around the zero value of `TimestampType` ### What changes are included in this PR? Just a comment change `nanosecond -> second` ### Are these changes tested? No need to test ### Are there any user-facing changes? No Closes: apache#35770 * Closes: apache#35770 Authored-by: ismail simsek <ismailsimsek09@gmail.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
JerAguilon
pushed a commit
to JerAguilon/arrow
that referenced
this issue
Oct 23, 2023
…s seconds in comment (apache#37905) ### Rationale for this change To clear the confusion around the zero value of `TimestampType` ### What changes are included in this PR? Just a comment change `nanosecond -> second` ### Are these changes tested? No need to test ### Are there any user-facing changes? No Closes: apache#35770 * Closes: apache#35770 Authored-by: ismail simsek <ismailsimsek09@gmail.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this issue
Nov 13, 2023
…s seconds in comment (apache#37905) ### Rationale for this change To clear the confusion around the zero value of `TimestampType` ### What changes are included in this PR? Just a comment change `nanosecond -> second` ### Are these changes tested? No need to test ### Are there any user-facing changes? No Closes: apache#35770 * Closes: apache#35770 Authored-by: ismail simsek <ismailsimsek09@gmail.com> Signed-off-by: Matt Topol <zotthewizard@gmail.com>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
…s seconds in comment (apache#37905) ### Rationale for this change To clear the confusion around the zero value of `TimestampType` ### What changes are included in this PR? Just a comment change `nanosecond -> second` ### Are these changes tested? No need to test ### Are there any user-facing changes? No Closes: apache#35770 * Closes: apache#35770 Authored-by: ismail simsek <ismailsimsek09@gmail.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
Bug
The godoc mentions the zero value of
arrow.TimestampType
should be nanosecond UTC (see https://github.com/apache/arrow/blob/main/go/arrow/datatype_fixedwidth.go#L340) but thearrow.TimeUnit
seems to default to seconds (https://github.com/apache/arrow/blob/main/go/arrow/datatype_fixedwidth.go#L327)output:
Component(s)
Go, Arrow v13
The text was updated successfully, but these errors were encountered: