jiayuasu opened a new pull request, #494: URL: https://github.com/apache/parquet-format/pull/494
<!-- 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 Update the specification to offer clearer instructions on how writers should populate bounding box values in the presence of NaNs, and how readers should interpret missing or incomplete bounding boxes. ### What changes are included in this PR? Added comments in the `Bounding Box` section of the `Geospatial.md`. Below is an example illustrating how bounding box statistics behave based on the presence of X and Y values: ``` --- Parquet file file-level bbox: [1, 8, 100, 800] -- Row group 1 row-group bbox 1: [1, 2, 100, 100] POINT (1, 100) POINT (2. NaN) -- Row group 2 row-group bbox 2: [3, 3, 300, 300] POINT (3, 300) POINT (NaN, NaN) -- Row group 3 row-group bbox 3: no bbox POINT (5, NaN) POINT (6, NaN) -- Row group 4 row-group bbox 4: [7, 8, 700, 800] POINT (7, 700) POINT (8, 800) -- Row group 5 row-group bbox 5: no bbox POINT (NaN, NaN) POINT (NaN, NaN) ``` ### Do these changes have PoC implementations? Yes, https://github.com/apache/parquet-java/pull/2971 and https://github.com/apache/arrow/pull/45459 <!-- 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]
