singhpk234 commented on PR #11165: URL: https://github.com/apache/iceberg/pull/11165#issuecomment-2366902023
The particular case referred here makes sense but was thinking if this is something we need to handle broadly ? IMHO we are lacking the exception handling entirely here for ex: 1/ What if it's 403 forbidden ? let;s say we have read only permission 2/ What if it;s service unavailable or rate limit exceeded etc @amogh-jahagirdar was thinking if we can re-use / generalize this code or classification [1] and wire it to all all glue-clients request / response interaction, your thoughts ? https://github.com/apache/iceberg/blob/main/aws/src/main/java/org/apache/iceberg/aws/glue/GlueTableOperations.java#L353 -- 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-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
