The current definition of the call detail table does not use a partitioned primary index:
CREATE TABLE calldetail (
phone_number DECIMAL(10) NOT NULL,
PRIMARY INDEX (phone_number, call_start);
Can the standard query workloads against this table be optimized by partitioning its primary index?