stefan-grafberger opened a new pull request, #635: URL: https://github.com/apache/parquet-format/pull/635
<!-- Thanks for opening a pull request! If you're new to Parquet-Format, information on how to contribute can be found here: https://parquet.apache.org/docs/contribution-guidelines/contributing Please open a GitHub issue for this pull request: https://github.com/apache/parquet-format/issues/new/choose and format pull request title as below: GH-${GITHUB_ISSUE_ID}: ${SUMMARY} or simply use the title below if it is a minor issue: MINOR: ${SUMMARY} --> ### Rationale for this change #603 allows a reader to resolve a value that sets both `inline` and a locator from either, so engines can return different bytes for the same value once the object at `uri` changes. ### What changes are included in this PR? - Restores the #585 wording that, if `inline` is set, the locator fields are provenance only, and keeps #603's clarification that both may be set. - Drops the expectation that producers write the same bytes in both, which readers cannot check and an overwrite of the object at `uri` breaks. - Allows `size` with `inline` alone, as its length. - Defines what `checksum` describes when `inline` and `uri` are both set. No existing value becomes invalid, and for values that set both `inline` and a locator, readers may only return `inline`. ### Do these changes have PoC implementations? Hardwood ([hardwood#1494](https://github.com/hardwood-hq/hardwood/pull/1494)) already reads `inline` first when it is set. <!-- Please uncomment the line below and replace ${GITHUB_ISSUE_ID} with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> -- 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]
