laserninja opened a new issue, #11584: URL: https://github.com/apache/gravitino/issues/11584
### What would you like to be improved? `IcebergConfigOperations` advertises a hardcoded `DEFAULT_ENDPOINTS` list (including `V1_SUBMIT_TABLE_SCAN_PLAN`) for every catalog, regardless of whether the configured backend actually supports those operations. A client that trusts the advertised `endpoints` may call an operation the backend cannot serve, producing confusing runtime errors. ### How should we improve? Derive the advertised endpoint set from the backing catalog's capabilities (e.g., gate optional endpoints like scan planning behind backend support) rather than a static list, while keeping the always-supported core endpoints. Add tests verifying the advertised set reflects backend capability. Related: IRC-at-scale epic #11131; spec-compliance epic #10547. -- 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]
