Major Description
- Cannot just replace index in PartitionConfiguration with an Set<Index> from Set<Object>
since PartitionConfiguration can be for any kind of partition.
- Any Partition can have hints provided on what attributes to index in it's own implementation
specific manner so something is needed for configuration yet it should not be an Index object
since this is specific to BTree based partitions. How do we enable this without causing issues?
Perhaps this is to be deferred to the partition implementation instead of providing it directly
in the superclass configuration bean for now?
- However some partitions may not index things at all if they are virtual partitions. So in this case
it seems we're better off leaving this property on the super class to be handled properly by subtypes.
I'm going to remove this property on the PartitionConfiguration and add it to the BTreePartitionConfiguration
for now and expect wiring to handle it properly based on the type of the partition.