stevenzwu opened a new pull request, #19070:
URL: https://github.com/apache/iceberg/pull/19070

   This reverts commit ea47af380c (#18394).
   
   #18394 reads geo bounds as GeospatialBound. Projecting a subset of the 
coordinates (for example, only lower_bound.m) stored M as X. See 
https://github.com/apache/iceberg/pull/18394#discussion_r4343444449. PR #18394 
worked around this by always projecting the full geo bound struct, which reads 
columns the caller did not request. @rdblue reached out offline and recommended 
that Iceberg shouldn't project additional data (like the entire bounds). 
   
   The spec says that if either the X or Y dimension is missing, the bounding 
box is not produced. GeospatialBound represents a bounding-box corner and 
should guarantee valid X and Y values, so it should not represent a partially 
projected bound. Making it projection-aware would also add a mutable StructLike 
with stats schema knowledge to the api module.
   
   Reverting restores the generic struct on the read path, which supports any 
projection without reading extra columns. GeospatialBound keeps the read-only 
StructLike used by the write path and continue to guarantee the XY coordinates. 
   
   Generated-by: Cursor (Claude Opus 5.5)


-- 
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]

Reply via email to