This PR clarifies how field resolution should happen when the base schema
does not perfectly match the file schema (this is a very common case in some
environments where there is no catalog or the catalog does not include the
full parquet schema).
This should not be a breaking change as all existing implementations are
operating by the default (name-based resolution) as far as I know.
This PR clarifies how field resolution should happen when the base schema does not perfectly match the file schema (this is a very common case in some environments where there is no catalog or the catalog does not include the full parquet schema).
This should not be a breaking change as all existing implementations are operating by the default (name-based resolution) as far as I know.