if there is a reason to separate data in the same table, differing column family and using locality groups is the best approach. Currently the way to vary column family is to change the adapter ID (feature type name), but it is unnecessary to persist the same adapter with different ID's if the feature type isn't really changing.
if there is a reason to separate data in the same table, differing column family and using locality groups is the best approach. Currently the way to vary column family is to change the adapter ID (feature type name), but it is unnecessary to persist the same adapter with different ID's if the feature type isn't really changing.