bobmerevel commented on issue #16838: URL: https://github.com/apache/iceberg/issues/16838#issuecomment-4722699372
That makes sense. I agree that at this layer the implementation cannot distinguish whether the null value originated from a REST Catalog response, another catalog implementation, or some other source. My main concern was the current failure mode: the action eventually fails with a NullPointerException, making the actual problem difficult to diagnose. Even if the error message is generic (for example, "Table metadata file location must not be null"), I think a fail-fast validation would still significantly improve the debugging experience for catalog implementers and users. If metadata-location becomes optional in the future, having such a guard would become even more valuable. @RussellSpitzer -- 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]
