Can the persistence order of a TimedDataPoint not be start?

#1

I have a type defined as:

@db(compactType=true,
    datastore='cassandra',
    partitionKeyField='parent',
    persistenceOrder='creationDate',
    persistDuplicates=false,
    shortId=true,
    shortIdReservationRange=100000)
entity type measurementA mixes TimedDataPoint<SeriesA>{
  parent: ~

  dataVersion: ~

  creationDate: !datetime

  start: ~

  value: int
}

I want to set the persistence order to be creationDate because I need to fetch the raw data by creationDate in a function. Will the performance of normalization be affected?

#2

Today we compact the timeseries (and timed) data points by converting the objects into a columnar structure and this helps us get huge compression (~10x) in comparison to storing raw objects. That will get affected when we try to change the persistence order

#3

@rohit.sureka Do you mean the performance won’t be affected, but more space will be needed? Do you have other suggestions about how to structure the data?

#4

Actually on checking deeper, it shouldn’t have any impact on normalization performance