Distributed Tables Compound Primary Keys Alternatives

Hi,

Is the compound primary keys (the table's primary key field + distribution field) to create a distributed table is a must? is there other way to create distributed table without having to modify the existing single column primary key into a compound one? perhaps by creating a unique index consisting of the compound fields should be enough to guarantee? Currently I'm using an ORM that doesn't (fully) support compound primary keys. Thanks.