scovich commented on issue #8086: URL: https://github.com/apache/arrow-rs/issues/8086#issuecomment-3165392839
> I personally suggest we follow the rules in the existing arrow [cast kernel](https://docs.rs/arrow/latest/arrow/compute/kernels/cast/index.html), likely simply calling that kernel for shredded values, and implementing the equivalent logic for unshredded variants. Thinking out loud here -- 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. However -- I _think_ the caller can just provide a schema where all leaf columns are VARIANT, if they want control over 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. -- 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
