With support for composite row keys, I am contemplating using a composite primary key to manage time series data and keep the columns "thin". This is to allow for Hive integration with my timeseries CF. The row key would look like this:
If I understand this correctly, my data would be bucketed by day and partitioned by day on the same nodes, hence I wouldn't get a performance penalty.
Is this assumption correct?