Craig Alvord

I guess translators aren't done yet. This is a relatively new set of strings, so I won't worry about adding a new bug. Moving this to Localization milestone.

@keen85 @pierrejeandev For anyone that's interested, we have a private build that adds date formatting to preview for Parquet files. Please give it a try and leave your feedback here....

@keen85 We can stick to ISO format unless we get additional feedback to the contrary. Our testing shows that `DATE`, `TIMESTAMP_MILLIS`, and `TIMESTAMP_MICRO` types should be parsed correctly. But from...

We will keep this item open to track the progress of those features. Not much else we can do until fixes/features become available.

Let's break this down a bit. There currently exist three different ways to represent timestamps in the Parquet format: Type | Description -----|:----------- `INT96` | These were originally intended to...

We started running into a build-related issue (see https://github.com/LibertyDSNP/parquetjs/issues/125).

@keen85 It turns out converting `INT96` values into ISO-formatted strings is a lot more complicated than I initially thought. ## Incorrect Assumptions At first, I assumed `INT96` values simply encoded...

@keen85 No apologies necessary! It was a perfectly valid request. We did our homework, and it turned out to be more work than we initially thought. All part of the...

The problem with timestamps is that they are converted to JavaScript `Date` objects for sorting. `Date` objects only have millisecond precision. Hence why timestamps that differ by a few nanoseconds...

String comparisons are a bit risky, as it's difficult to predict how locales will order certain characters. The Temporal API provides the necessary nanosecond precision and works beautifully, but comparing...