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
Related to Issue #16109 (very broken parquet files).
Can we please add "unit" tests (or rather integration tests) like this for every reader/writer (e.g., read/write_parquet, read/write_ndjson, etc.)? Ideally they'll run >10 times each with >10 different random generations, and perhaps a few different structures (some datetimes, etc.).
The non-deterministic failures in the write_parquet function could have been caught with this test, and it's so basic to implement and so useful in checking that the entire write-to-read path works properly.
Description
Related to Issue #16109 (very broken parquet files).
Can we please add "unit" tests (or rather integration tests) like this for every reader/writer (e.g.,
read/write_parquet
,read/write_ndjson
, etc.)? Ideally they'll run >10 times each with >10 different random generations, and perhaps a few different structures (some datetimes, etc.).The non-deterministic failures in the write_parquet function could have been caught with this test, and it's so basic to implement and so useful in checking that the entire write-to-read path works properly.
The text was updated successfully, but these errors were encountered: