Typical Scenarios of the HBase Cold and Hot Data Separation Sample Program
CloudTable HBase supports hot and cold data separation. With this feature, you can store hot and cold data in different types of storage media to reduce storage costs.
In a big data storage scenario, business data such as order data or monitoring data grows over time. As your business develops, such data can be of a large volume and rarely used. Companies may want to use cost-effective storage to store this type of data to reduce costs.
You can quickly learn and master the development process of HBase cold and hot data separation and know the functions of key APIs in a typical use case.
Scenario
Assume that a user develops an application to record and query weather information about a city in real time. The following table lists the recorded data.
City |
District |
Date |
Temperature |
Humidity |
---|---|---|---|---|
Shenzhen |
Longgang |
2017/7/1 00:00:00 |
28 |
54 |
Shenzhen |
Longgang |
2017/7/1 01:00:00 |
27 |
53 |
Shenzhen |
Longgang |
2017/7/1 02:00:00 |
27 |
52 |
Shenzhen |
Longgang |
2017/7/1 03:00:00 |
27 |
51 |
Shenzhen |
Longgang |
2017/7/1 04:00:00 |
27 |
50 |
Shenzhen |
Longgang |
2017/7/1 05:00:00 |
27 |
49 |
Shenzhen |
Longgang |
2017/7/1 06:00:00 |
27 |
48 |
Shenzhen |
Longgang |
2017/7/1 07:00:00 |
27 |
46 |
Shenzhen |
Longgang |
2017/7/1 08:00:00 |
29 |
46 |
Shenzhen |
Longgang |
2017/7/1 09:00:00 |
30 |
48 |
Shenzhen |
Longgang |
2017/7/1 10:00:00 |
32 |
48 |
Shenzhen |
Longgang |
2017/7/1 11:00:00 |
32 |
49 |
Shenzhen |
Longgang |
2017/7/1 12:00:00 |
33 |
49 |
Shenzhen |
Longgang |
2017/7/1 13:00:00 |
33 |
50 |
Shenzhen |
Longgang |
2017/7/1 14:00:00 |
32 |
50 |
Shenzhen |
Longgang |
2017/7/1 15:00:00 |
32 |
50 |
Shenzhen |
Longgang |
2017/7/1 16:00:00 |
31 |
51 |
Shenzhen |
Longgang |
2017/7/1 17:00:00 |
30 |
51 |
Shenzhen |
Longgang |
2017/7/1 18:00:00 |
30 |
51 |
Shenzhen |
Longgang |
2017/7/1 19:00:00 |
29 |
51 |
Shenzhen |
Longgang |
2017/7/1 20:00:00 |
29 |
52 |
Shenzhen |
Longgang |
2017/7/1 21:00:00 |
29 |
53 |
Shenzhen |
Longgang |
2017/7/1 22:00:00 |
28 |
54 |
Shenzhen |
Longgang |
2017/7/1 23:00:00 |
28 |
54 |
Shenzhen |
Longgang |
2017/7/2 00:00:00 |
28 |
54 |
Shenzhen |
Longgang |
2017/7/2 01:00:00 |
27 |
53 |
Shenzhen |
Longgang |
2017/7/2 02:00:00 |
27 |
52 |
Shenzhen |
Longgang |
2017/7/2 03:00:00 |
27 |
51 |
Shenzhen |
Longgang |
2017/7/2 04:00:00 |
27 |
50 |
Shenzhen |
Longgang |
2017/7/2 05:00:00 |
27 |
49 |
Shenzhen |
Longgang |
2017/7/2 06:00:00 |
27 |
48 |
Shenzhen |
Longgang |
2017/7/2 07:00:00 |
27 |
46 |
Shenzhen |
Longgang |
2017/7/2 08:00:00 |
29 |
46 |
Shenzhen |
Longgang |
2017/7/2 09:00:00 |
30 |
48 |
Shenzhen |
Longgang |
2017/7/2 10:00:00 |
32 |
48 |
Shenzhen |
Longgang |
2017/7/2 11:00:00 |
32 |
49 |
Shenzhen |
Longgang |
2017/7/2 12:00:00 |
33 |
49 |
Shenzhen |
Longgang |
2017/7/2 13:00:00 |
33 |
50 |
Shenzhen |
Longgang |
2017/7/2 14:00:00 |
32 |
50 |
Shenzhen |
Longgang |
2017/7/2 15:00:00 |
32 |
50 |
Shenzhen |
Longgang |
2017/7/2 16:00:00 |
31 |
51 |
Shenzhen |
Longgang |
2017/7/2 17:00:00 |
30 |
51 |
Shenzhen |
Longgang |
2017/7/2 18:00:00 |
30 |
51 |
Shenzhen |
Longgang |
2017/7/2 19:00:00 |
29 |
51 |
Shenzhen |
Longgang |
2017/7/2 20:00:00 |
29 |
52 |
Shenzhen |
Longgang |
2017/7/2 21:00:00 |
29 |
53 |
Shenzhen |
Longgang |
2017/7/2 22:00:00 |
28 |
54 |
Shenzhen |
Longgang |
2017/7/2 23:00:00 |
28 |
54 |
Data Planning
Proper design of a table structure, RowKeys, and column names enable you to make full use of HBase advantages. In this sample project, the city, region, and date are used as RowKeys, and columns are stored in the info column family.
Data is written on the hour of the current day. The data of the previous day is seldom accessed and is automatically archived to the cold storage to save storage space.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot