[I] investigate better API structure for RewriteTablePathUtil [iceberg]

["kevinjqliu (via GitHub)" <gi...@apache.org>]

kevinjqliu opened a new issue, #16983:
URL: https://github.com/apache/iceberg/issues/16983

   Ok I don't think we need to do it in this PR but after looking at this, these APIs are getting pretty unfortunate, we're passing in 10 arguments now. 
   
   I think we'll want to introduce some builders and some structure like RewriteContext, and have structures which kick back things like a DeleteManifestRewriter. 
   
   I think what I'm asking here is more fundamental changes (and possibly an overhaul/elimination of this Util class) so like I said, definitely for something in the future.
   
   _Originally posted by @amogh-jahagirdar in https://github.com/apache/iceberg/pull/15470#discussion_r3486737112_
               


-- 
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: issues-unsubscribe@iceberg.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org