SAY-5 commented on PR #808: URL: https://github.com/apache/arrow-go/pull/808#issuecomment-4432909117
I'd lean toward doing the Arrow union type support as a follow-up. This PR is intentionally narrow: it just turns the silent data-loss case (non-nullable unions being dropped) into a clear error, which is a safe incremental step. Mapping Avro unions onto `arrow.UnionType` (dense vs sparse, type-id assignment, the reader/writer plumbing) is a meatier change that deserves its own PR and tests. Happy to open a tracking issue for it if you'd like. -- 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]
