Support for multi-temperature data - part 1

Registered by Hans Zeller on 2014-11-19

Databases that maintain current and historical data often suffer from the problem of decreasing performance as the amount of historical data grows. Most database systems have features that avoid this performance and scalability problem, typically by ensuring that the recent (or “hot”) data is stored separately from the older (“cold”) data. We want to implement multi-temperature data by creating logical, not physical range partitions. We do this by adding the range partition number as a prefix to the key, so that hot data is stored together in a key range and that cold data is stored in a separate key range. We expect that these logical range partitions will exist within each region, and that this is achieved by salting. The range partition number is a computed system column, meaning that it is not normally user-visible and that it is automatically maintained by Trafodion.

Blueprint information

Status:
Started
Approver:
Suresh Subbiah
Priority:
Medium
Drafter:
Hans Zeller
Direction:
Approved
Assignee:
Hans Zeller
Definition:
Approved
Series goal:
None
Implementation:
Beta Available
Milestone target:
milestone icon r1.0
Started by
Hans Zeller on 2014-11-19

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.trafodion.org/#q,topic:bug/1388458,n,z

Addressed by: https://review.trafodion.org/741
    Support for divisioning (multi-temperature data)

The logical partition approach will be difficult to support both "DIVISION BY" and "PARTITION BY" on a table, where partition key and division key are different.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.