[ARROW-16543] [JS] Timestamp types are all the same

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: JavaScript
• External issue URL: https://github.com/apache/arrow/issues/31904

Language

javascript

• Assignee: Unassigned
• Reporter: Teodor Kostov
• Created: 12/May/22 09:42
• Updated: 11/Jan/23 11:44

Description

Current timestamp types are all the same. They have the same representation. And also the same precision.

For example, TimestampSecond and TimestampMillisecond return the values as 1652118180000. Instead, I would expect the TimestampSecond to drop the 3 zeros when returning a value, e.g. 1652118180. Also, the representation underneath is still an int32 array. Even though for TimestampSecond 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 TimestampNanosecond - TypeError: can't convert 1652118180000 to BigInt.