Partitioning

Availability

This feature is available since MogDB 1.1.0.

Introduction

Data is partitioned horizontally on a node using a specified policy. This operation splits a table into multiple partitions that are not overlapped.

Benefits

In common scenarios, a partitioned table has the following advantages over a common table:

• High query performance: You can specify partitions when querying partitioned tables, improving query efficiency.
• High availability: If a certain partition in a partitioned table is faulty, data in the other partitions is still available.
• Balanced I/O: Partitions can be mapped to different disks to balance I/O and improve the overall system performance.

Description

Currently, MogDB supports range partitioned tables, list partitioned tables, and hash partitioned tables.

• In a range partitioned table, data within a certain range is mapped to each partition. The range is determined by the partition key specified when the partitioned table is created. This partitioning mode is most commonly used.

  With the range partitioning function, the database divides a record, which is to be inserted into a table, into multiple ranges using one or multiple columns and creates a partition for each range to store data. Partition ranges do no overlap.

• In a list partitioned table, data is mapped to each partition based on the key values contained in each partition. The key values contained in a partition are specified when the partition is created.

  The list partitioning function divides the key values in the records to be inserted into a table into multiple lists (the lists do not overlap in different partitions) based on a column of the table, and then creates a partition for each list to store the corresponding data.

• In a hash partitioned table, data is mapped to each partition using the hash algorithm, and each partition stores records with the same hash value.

  The hash partitioning function uses the internal hash algorithm to divide records to be inserted into a table into partitions based on a column of the table.

If you specify the PARTITION parameter when running the CREATE TABLE statement, data in the table will be partitioned. Users can modify partition keys as needed during table creation to make the query result stored in the same or least partitions (called partition pruning), obtaining consecutive I/O to improve the query performance.

In actual services, time is often used to filter query objects. Therefore, you can select the time column as the partition key. The key value range can be adjusted based on the total data volume and the data volume queried at a time.

Enhancements

Range partitioned tables can be combined.

The list and hash partitioned tables support data exchange.

Constraints

None.

Dependencies

None.