alamb commented on PR #7403: URL: https://github.com/apache/arrow-rs/pull/7403#issuecomment-2809170590
> I agree something like arrow-compute makes a lot of sense. Unfortunately, the tape decoder machinery is private to arrow-json crate, so I had to do the initial pathfinding here. Is there a better way forward? SOme other options might be (not sure which one we should go with): 1. copy/paste the code to avoid a dependency 2. refactor the tape machinery into a new crate that they can both depend on I have been thinking a lot about how we should introduce variant. What do you think about a structure like this (crates) - `variant`: Core definition of the open variant type, no dependencies - `arrow-variant`: Arrow extension type for variant, including conversion to/from JSON and arrow arrays (e.g. a compute kernel, etc) I think depending on how arrow-variant is implemented, maybe it depends directly on `arrow-json` and maybe expose relevant parts -- 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
