Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
Description
According to ARROW-15899, it is possible to declare a field non-nullable, associate with data that has nulls, and still pass validation.
Validation should instead fail in such a situation (at least full validation, since computing the null count can be O(n)).
Attachments
Issue Links
- is related to
-
ARROW-16116 [C++] Properly handle non-nullable fields in Parquet reading
- Resolved
- relates to
-
ARROW-15899 [C++] Parquet writes broken file or incorrect data when nullable=False
- Open
- links to