You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a better Offload Transport splitter for PREDICATE_AND_RANGE offloads. Currently we select ROWID range splitting and the ROWID ranges generated are for the whole table. The predicate is likely for a very small portion of the table.
When using PREDICATE_AND_RANGE we mandate that the predicate contains the partition key, therefore we should be able to apply that to the list of not-yet-Offloaded partitions and identify which partitions satisfy the data for the predicate. Doing this would make the feature much more performant.
For non-partitioned tables with a numeric primary key singleton we could utilise id range splitting like we do for IOTs.
The text was updated successfully, but these errors were encountered:
We need a better Offload Transport splitter for PREDICATE_AND_RANGE offloads. Currently we select ROWID range splitting and the ROWID ranges generated are for the whole table. The predicate is likely for a very small portion of the table.
When using PREDICATE_AND_RANGE we mandate that the predicate contains the partition key, therefore we should be able to apply that to the list of not-yet-Offloaded partitions and identify which partitions satisfy the data for the predicate. Doing this would make the feature much more performant.
For non-partitioned tables with a numeric primary key singleton we could utilise id range splitting like we do for IOTs.
The text was updated successfully, but these errors were encountered: