zeroshade commented on issue #1178: URL: https://github.com/apache/iceberg-go/issues/1178#issuecomment-6020955787
> Server scan-planning-mode directive. Java gives the server's value precedence over the client's and fails if server is required but the plan endpoint isn't advertised (RESTSessionCatalog.restTableForScanPlanning). We currently ignore the directive, and the README documents that. Should we match Java, or keep the documented divergence? https://github.com/apache/iceberg-go/pull/2094 exposes the directive on Table but doesn't enforce it. Let's match Java's behavior where possible. > Incremental remote scans. start-snapshot-id/end-snapshot-id aren't implemented, and incremental append and changelog scans return an error in remote mode. Java's RESTTable only overrides newScan(), so Java's incremental scans plan locally as well. Should this be a follow-up issue, or out of scope? My vote is for a follow-up issue here. > CLI adoption. This is more than adding a flag: files walks manifests directly, and the maintenance commands need more than a normal scan. Should it be a follow-up issue, or out of scope? My vote is also for a follow-up issue, but i'm okay with it being out of scope -- 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]
