Oracle: index-driven backfills for tables without primary keys
When primaryKeysOverride points to a unique index, Oracle backfill queries include an index hint so the optimizer uses that index instead of a full scan.
Oracle tables that lack a primary key but have a unique index were falling back to full table scans during backfill, making snapshots extremely slow.
When primaryKeysOverride points to a unique index, Artie now injects an index hint into backfill queries to force the Oracle optimizer to use that index.
Why this matters
- Restores index-driven performance for Oracle backfills on keyless tables
- No additional configuration required beyond the existing
primaryKeysOverridesetting