You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you load a table using aq.fromArrow, date type information is preserved;
but after some operations, the dates revert to being represented as some kind of integers, not as datetime.
Apologies for not providing an example inline, because I'm not confident about generating
an Arrow date field in Javascript. In the notebook at https://observablehq.com/@bmschmidt/a-files,
you can see that date information is preserved after a filter
I should clarify that this situation seems to hold with {unpack: true} and {unpack: false}.
I'm also confused about what these numbers mean -- I would have thought milliseconds since Unix epoch which arrow uses as backing, but they are not. (All of the people in that particular collection were born before 1920, but many of the integers are positive.)
Thanks again for this great library.
If you load a table using aq.fromArrow, date type information is preserved;
but after some operations, the dates revert to being represented as some kind of integers, not as datetime.
Apologies for not providing an example inline, because I'm not confident about generating
an Arrow date field in Javascript. In the notebook at https://observablehq.com/@bmschmidt/a-files,
you can see that date information is preserved after a filter
gives
But after a sample or slice, you get ints:
gives
The text was updated successfully, but these errors were encountered: