Skip to content

Core: Simplify RESTTableScan by removing catalog internals#15595

Draft
singhpk234 wants to merge 1 commit intoapache:mainfrom
singhpk234:feature/clean-up-rest-scan-planning
Draft

Core: Simplify RESTTableScan by removing catalog internals#15595
singhpk234 wants to merge 1 commit intoapache:mainfrom
singhpk234:feature/clean-up-rest-scan-planning

Conversation

@singhpk234
Copy link
Contributor

@singhpk234 singhpk234 commented Mar 12, 2026

Address #15561 (comment)

  • Remove redundant fields (table, operations, tableIO) from RESTTableScan
  • Replace catalogProperties + hadoopConf with a FileIO factory function
  • Pre-compute resource paths instead of passing ResourcePaths + TableIdentifier
  • Replace Set with supportsAsync/supportsCancel/supportsFetchTasks booleans
  • Change headers from Map to Supplier for consistency with RESTTable
  • Fix newRefinedScan to not propagate plan-scoped FileIO
  • Fix cleanupPlanResources to always invalidate tracker

- Remove redundant fields (table, operations, tableIO) from RESTTableScan
- Replace catalogProperties + hadoopConf with a FileIO factory function
- Pre-compute resource paths instead of passing ResourcePaths + TableIdentifier
- Replace Set<Endpoint> with supportsAsync/supportsCancel/supportsFetchTasks booleans
- Change headers from Map to Supplier for consistency with RESTTable
- Fix newRefinedScan to not propagate plan-scoped FileIO
- Fix cleanupPlanResources to always invalidate tracker
Endpoint.check(supportedEndpoints, Endpoint.V1_FETCH_TABLE_SCAN_PLAN);
Preconditions.checkState(
supportsAsync,
"Invalid plan status SUBMITTED: server does not support async scan planning");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUBMITTED is not a valid status. It is submitted and I think it is important to be consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants