You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Teodor Kostov (Jira)" <ji...@apache.org> on 2022/05/12 09:43:00 UTC
[jira] [Created] (ARROW-16543) [JS] Timestamp types are all the same
Teodor Kostov created ARROW-16543:
-------------------------------------
Summary: [JS] Timestamp types are all the same
Key: ARROW-16543
URL: https://issues.apache.org/jira/browse/ARROW-16543
Project: Apache Arrow
Issue Type: Bug
Components: JavaScript
Reporter: Teodor Kostov
Current timestamp types are all the same. They have the same representation. And also the same precision.
For example, {{TimestampSeconds}} and {{TimestampMilliseconds}} return the values as {{1652118180000}}. Instead, I would expect the {{TimestampSeconds}} to drop the 3 zeros when returning a value, e.g. {{1652118180}}. Also, the representation underneath is still an {{int32}} array. Even though for {{TimestampSeconds}} every second value is {{0}}, the array still has double the amount of integers.
I also got an error when trying to read a {{Date}} as {{TimestampNanoseconds}} - {{TypeError: can't convert 1652118180000 to BigInt}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)