alamb commented on issue #563: URL: https://github.com/apache/parquet-format/issues/563#issuecomment-4579282567
> In that case, I think that we need to plan how to handle that compatibility issue. I don't think it is okay to leave this up to writers without clear guidance. In my mind, this is no different than other newly added features such as byte_stream_spit encoding or V2 data pages: If a writer writes a file that uses a feature that older readers don't know how to handle, then the older software can't read it. As you say this is a choice the writer has to make. I agree clear guidance / communication is important, and I think it is what https://parquet.apache.org/docs/file-format/implementationstatus/ provides (namely, writers can choose what feature set at what version of older readers they want to target) Making that a bit more formulaic / explicit would probably be good -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
