Errors that may occur when Tablestore Reader is running - Tablestore

This topic describes the errors that may occur when Tablestore Reader is running and how to troubleshoot the errors.

Error message: "Input size of values not equal size of primary key. input size: xx, primary key size: xx"

Problem description
The "Input size of values not equal size of primary key. input size: xx, primary key size: xx" error message appears when Tablestore Reader is running. The following figure shows the error message.
Possible cause
The number of primary key columns that are specified in the Tablestore Reader script is different from that in the Tablestore data table.
Solution
Check the schema of the Tablestore data table, obtain the number of primary key columns in the data table, and then set the obtained value as the number of primary key columns in the Tablestore Reader script.
For example, a Tablestore data table contains two primary key columns and you want to synchronize all data in the table. The following sample code shows how to specify the number of primary key columns in the Tablestore Reader script:
```
"range": {
  "begin": [
    {
      "type": "INF_MIN"
    },
    {
      "type": "INF_MIN"
    }
  ],
  "end": [
    {
      "type": "INF_MAX"
    },
    {
      "type": "INF_MAX"
    }
  ]
}
```

Problem description
The "Input type of 'range-split' not match partition key. Item of 'range-split' type:xx, Partition type:xx" error message appears when Tablestore Reader is running. The following figure shows the error message.
Possible cause
The split point is incorrectly configured in the Tablestore Reader script. The following sample code shows how the split point is incorrectly configured:
```
"split": [
  {
    "type": "INF_MIN"
  },
  {
  "type": "INF_MAX"
  }
]
```
Solution
- Delete the split point configuration from the Tablestore Reader script.
- Configure the split point again. For more information, see Configure split points when I use Tablestore Reader to synchronize full data.

Problem description
The "Invalid 'column', Can not parse Object to 'OTSColumn', item of list is not a map" error message appears when Tablestore Reader is running. The following figure shows the error message.
Possible cause
The column parameter is incorrectly specified in the Tablestore Reader script. The following sample code shows how the column parameter is incorrectly specified:
```
"column": [
  "id",
  "name",
  "age"
]
```
Solution
Make sure that the column parameter is correctly specified in the Tablestore Reader script. The following sample code shows how to specify the column parameter:
```
"column": [
  {
    "name": "id"
  },
  {
    "name": "name"
  },
  {
    "name": "age"
  }
]
```