pitrou commented on issue #384: URL: https://github.com/apache/parquet-format/issues/384#issuecomment-3406558108
I think this idea is still worth pursuing, but it needs to be defined more objectively. I would propose the following abstract mechanism: 1. Decide on a small set of "primary" implementations (for example: Parquet Java, Parquet Rust, Parquet C++) 2. List all optional Parquet features 3. For each feature, list the version of each primary implementation where it was first made available **for reading** 4. For each primary implementation, map the listed versions to release dates 5. Define calendar-based "compliance levels" or "presets": for example, the "2022" preset would include all features readable by all primary implementations by 2022-01-01 This could be automated by a relatively simple Python script with a separate JSON or YAML file. What do you think about this rough idea? @wgtmac @alamb @tustvold @julienledem @Fokko @etseidl -- 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]
