Partitioned index by range or hash - Which option?

 I have a large volume table that I plan to range partition. The table has an id column as the primary key and another id column that I plan to partition by (it is not part of the primary key).

This table is a parent table and I plan to have multiple child tables use reference partitioning back to the parent.

I'm stumped on what kind of index strategy to use for the primary key for the parent table.

Global partioned index by range, global partitioned index by hash, or global nonpartitioned index.

Option 1: Use global partitioned index by range - I have to create tons of index partitions and I don't know the daily volume of the lineitemid, this doesn't seem practical.Having the ids stored together in the index partition by date makes sense.