raulcd commented on code in PR #49554: URL: https://github.com/apache/arrow/pull/49554#discussion_r2960831845
########## docs/source/format/Intro.rst: ########## @@ -296,6 +296,13 @@ key is the field name and the child array its values. The field (key) is saved in the schema and the values of a specific field (key) are saved in the child array. +Since child arrays are independent, Arrow does not enforce physical +consistency between the struct's validity bitmap and those of it's children. +Logically, a struct row is only valid if both the parent and the child +bitmaps have a value of 1 for that slot (a logical AND operation). +This allows for "hidden" data to exist in child arrays at null struct Review Comment: I would personally remove the term `hidden` as it might give connotations of obfuscation/security related and this is not the intention, the intention is more about avoiding copy and reusing existing buffers. The data is just left in place because it's cheaper: ```suggestion This allows for data to exist in child arrays at null struct ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
