alamb commented on issue #8086: URL: https://github.com/apache/arrow-rs/issues/8086#issuecomment-3165521525
> The engine and/or user may have very different opinions than arrow about casting semantics, which is why I've been concerned about "just" doing a `cast` internally. Even with cast options I don't think it gives enough control. In my opinion since this is all in the context of parquet-variant-compute -- namely manipulating variants using Arrow arrays -- I think it is actually fine to only provide arrow casting semantics. > The resulting VariantArray would come back unchanged in its original form (shredded or unshredded). At worst, we might have to extract a subset of bytes if some requested leaf path penetrated an unshredded field. Yes, this is my ideal outcome -- that the library is flexible enough people can implement whatever semantics if what is provided by variant_get is insufficient -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
