Hi Ken, We did initially consider an approach similar to what you suggest, but decided not to go with it due to complexities when the number of mappers is different to the number of partitions. Instead we are breaking up the blocks in the table and spreading them across all the mappers and doing ROWID range scans. So all mappers could be reading from all partitions - but they would only be reading part of each. Splitting by PARTITION may provide slightly better performance, but we don't believe it would be a huge difference.
Regards, Peter Hall Quest Software
