Thanks all!
So, in general:
1. For our Binary Like [1] format, and List formats [2], if the parent is
not valid, the offset should still be valid
2. For the StringView ListView [3] types arrow is currently working on,
if the parent is not valid, the child might has valid content
Am I right? And can I add corresponding words to the validity part in the
document[4]?
[1]
https://arrow.apache.org/docs/format/Columnar.html#variable-size-binary-layout
[2]
https://arrow.apache.org/docs/format/Columnar.html#variable-size-list-layout
[3] https://lists.apache.org/thread/c6frlr9gcxy8qdhbmv8cn3rdjbrqxb1v
[4] https://arrow.apache.org/docs/format/Columnar.html#validity-bitmaps
Thanks,
Xuwei Fu
On 2023/06/28 15:03:11 wish maple wrote:
> Hi,
>
> By looking at the arrow standard, when it comes to nested structure, like
> StructArray[1] or FixedListArray[2], when parent is not valid, the
> correspond child leaves "undefined".
>
> If it's a BinaryArray, when when it parent is not valid, would a validity
> member point to a undefined address?
>
> And if it's ListArray[3], when it parent is not valid, should it offset
and
> size be valid?
>
> Thanks,
> Xuwei Fu
>
> [1] https://arrow.apache.org/docs/format/Columnar.html#struct-layout
> [2]
> https://arrow.apache.org/docs/format/Columnar.html#fixed-size-list-layout
> [3]
>
https://arrow.apache.org/docs/format/Columnar.html#variable-size-list-layout
>
