I think using the default schema mapper makes sense for now / in this PR, but in general I think it would make sense to allow the user to provide their own schema mapping rules here (so a default value that is not `NULL` can be used, for example) via their own mapper.
(this is not a change needed for this PR, I just noticed it while reviewing this PR)
However, we woudl have to add a schema mapper factory to
ListingOptionshttps://github.com/apache/datafusion/blob/f1bbb1d636650c7f28f52dc507f36e64d71e1aa8/datafusion/core/src/datasource/listing/table.rs#L256-L255
(this is not a change needed for this PR, I just noticed it while reviewing this PR)
Originally posted by @alamb in #15865 (comment)