On Thu, 9 Apr 2026 at 11:35, Andrew Lamb <[email protected]> wrote:
> > It seems like at very least we could do is make a PR to parquet-java to > stop needing `path_in_schema`. > > +1 > And then we could add some info to the spec explaining older readers might > need it, but newer readers might choose not to populate it if they wanted > to reduce their metadata size (at the expense of older readers not being > able to read it) > > +1 It'd be good for parquet cli tools to log when the field is missing, so it's easy to check for a file being compatible with older releases before shipping and waiting for complaints. Steve
