Revanth14 opened a new issue, #2152: URL: https://github.com/apache/iceberg-go/issues/2152
### Feature Request / Improvement Follow-up to #1178, per discussion with @laskoviymishka. This needs alignment on the Java side before we commit to a shape. Nothing here is urgent. **Today** - `PlanTableScanRequest` deliberately omits the spec's `start-snapshot-id` and `end-snapshot-id` fields, and the rule that a request sets either `snapshot-id` or that pair, not both (`catalog/rest/scan_planning.go`). - `NewIncrementalAppendScan` and `NewIncrementalChangelogScan` return an error in `ScanPlanningRemote` mode, and fall back to local in `ScanPlanningAuto` mode. **Java** - `RESTTable` only overrides `newScan()`, so Java's incremental-scan APIs plan locally. - `RESTTableScan` does send `start-snapshot-id`/`end-snapshot-id`, with `use-snapshot-schema=true`, when the scan context carries a from-snapshot. **Open questions** 1. Which Go incremental APIs should support remote planning: append only, or changelog too? -- 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]
