Currently if there's no tid index in the table, the storage module adds an internal _tid parameter. We need to stop doing that, because for the indexing tables in the new storage design we don't need the TID as an index, we index by timestamp.
|Resolved||Eevans||T169936 Services 2017/18 Q1 goal: Start gradual roll-out of Cassandra 3 & new schema to resolve storage scaling issues and OOM errors.|
|Resolved||Eevans||T169938 End of July milestone: Initial implementation & start of testing|
|Resolved||Pchelolo||T170902 Don't add the TID by default in storage module|
Right now we can get away from this by using the timeuuid as an index in the timeline tables as we can create TIDs for arbitrary dates. However, the plan for the key_value buckets was to start simply overwriting the content, so this automatic generation of a tid will get in our way..