Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
The followup to actually fix this is ARROW-17809 (the first try was ARROW-17643). It is likely a DuckDB problem; however, it's difficult to diagnose and will take some time. In the meantime, we should just skip the test because it is obscuring other failures.
Attachments
Issue Links
- links to