# Reading of Clustered Index Table

![`smart`](WritingOperationofNonclusteredIndexTable04_aa_002_20230905.png)

```
CREATE TABLE T (
 ID int not null PRIMARY KEY,
 Name varchar(20),
 tel varchar(16),
);
insert into T values ( 1, 'Tom', '7073958726');
insert into T values ( 2, 'Jack', '4782733578');
insert into T values ( 3, 'Frank', '147810546');
insert into T values ( 4, 'Tony', '335451143');
insert into T values ( 5, 'Jim', '1390811212');
insert into T values ( 6, 'Sam', ‘1579915611');
```
----------------------------------------------------
The current table T is a Clustered Index Table. The table creation statement is as follows:
```
CREATE TABLE T (
 ID int not null PRIMARY KEY,
 Name varchar(20),
 tel varchar(16),
);
insert into T values ( 1, 'Tom', '7073958726');
insert into T values ( 2, 'Jack', '4782733578');
insert into T values ( 3, 'Frank', '147810546');
insert into T values ( 4, 'Tony', '335451143');
insert into T values ( 5, 'Jim', '1390811212');
insert into T values ( 6, 'Sam', ‘1579915611');
```
Note that for a table with a defined primary key, if the CLUSTERED keyword is not added, it will default to being a Clustered Index Table.
In the slide, there are 2 Regions with the leader role for the key-value pairs of the table, distributed across 2 TiKV nodes. Since the data in Clustered Index Tables is stored in an ordered manner according to the structure of the primary key, we can consider the Key in the table as the primary key itself, so there is no need to store the primary key separately! Now, let's proceed with the read operation.