GoogleCloudPlatform / GoogleCloudPlatform/spanner-migration-tool

Mismatch in scanned row count from DynamoDB database

Open
#352 0 comments 0 reactions 0 assignees View on GitHub
p4
Dominant language
PLpgSQL
Stars
155
Forks
83
Avg merge
3d 7h
Merged PRs (30d)
6

Description

## Issue

The number of rows scanned while performing migration doesn't match with the actual number of rows present in the DynamoDB database.

## Steps which led to the Problem

1. Dynamodb database table consisted of 11500 rows.
![Screenshot 2022-07-20 11 18 09 AM](https://user-images.githubusercontent.com/105852100/179906787-0b64a98c-3b46-450c-8c44-be5d95e80406.png)
1. Performed bulk migration using HarbourBridge.
1. Only 4511 rows were scanned for writing to Cloud Spanner.
![Screenshot 2022-07-20 11 26 30 AM](https://user-images.githubusercontent.com/105852100/179907578-32e990ec-e9b0-4567-b135-56a44b0706d8.png)
**Note**: This statement was only printed to debug and not printed while performing actual migration.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.