lidavidm commented on issue #3134: URL: https://github.com/apache/arrow-adbc/issues/3134#issuecomment-3061733405
Is this only nullability mismatches? Or is it other things, too? For nullability, I guess I wonder why Dremio doesn't just always return all fields and data as "nullable" up front to avoid this issue (and Dremio designed Flight SQL!) It would be rather concerning to simply ignore nullability, too. If we were to add a flag, it would be (IMO) a statement option that casts all fields (and child fields?) to `nullable`, and not something that just ignores nullability (otherwise you may end up with nulls in a schema that is declared not null) (but this may get wonky in the general case: for some types, like maps, some child fields must not be nullable, and possibly changing the nullability of an extension field is also dangerous). -- 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
