scovich commented on issue #8153: URL: https://github.com/apache/arrow-rs/issues/8153#issuecomment-4093498719
@sdf-jkl your assessment makes sense to me. I think we even had conversations in the past about a utility method to expand a "logical" shredding schema into the equivalent physical shredding schema. As in, caller provides a struct that matches the desired shredding (what paths to shred as struct, int, string, etc vs leave as unshredded variant), and the utility spits out the corresponding arrangement of value and typed_value column pairs. We didn't pursue it back then because there was no way to know if we had a physical variant schema vs. a normal struct that happened to look variant-ish. Now that we have the variant extension type, a quick metadata check should distinguish the two and we could do what you say. Even better -- given the recursive nature of variant_get, we "should" get the mixed scenario "for free" once we have support for the two base cases. -- 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]
