Currently the --partition-name option means offload partitions up to and including --partition-name when used on a RANGE table.
It would be useful for customers to be able to deal with a RANGE partitioned table one partition at a time. Effectively treating a RANGE table as LIST. We already have the opposite concept.
This issue proposes the following:
- Add a new option
--range-partition-name which, for RANGE incremental tables, takes on the functionality of the current --partition-name option
- Reimplement
--partition-name for RANGE incremental tables to mean offload exactly one partition. Considerations:
a) We need a new OFFLOAD_TYPE for these partitionwise offloads, maybe RANGE_AS_LIST?
b) For an already RANGE offloaded table we cannot allow this option
c) If any data for the partition to be offloaded exists in the target then we need to reject it
Currently the
--partition-nameoption means offload partitions up to and including--partition-namewhen used on a RANGE table.It would be useful for customers to be able to deal with a RANGE partitioned table one partition at a time. Effectively treating a RANGE table as LIST. We already have the opposite concept.
This issue proposes the following:
--range-partition-namewhich, for RANGE incremental tables, takes on the functionality of the current--partition-nameoption--partition-namefor RANGE incremental tables to mean offload exactly one partition. Considerations:a) We need a new OFFLOAD_TYPE for these partitionwise offloads, maybe RANGE_AS_LIST?
b) For an already RANGE offloaded table we cannot allow this option
c) If any data for the partition to be offloaded exists in the target then we need to reject it