Classification
On publishing to the Ledger user interface, each card is classified according to whether all reported statistics are identical or do not match. Those classifications are listed as a match or mismatch.
Matches occur when all statistics are in sync. This means that the same amount of data was sent from the application and is ingested in Data Lake. The checksum verification is correct and the row count in both is the same.
This table shows a match scenario:
| Difference (Data Lake/Compass – Application count) | Difference |
|---|---|
|
Checksum verification |
0 (Correct) |
|
Instance count |
0 |
|
Row count |
0 |
|
Classification |
match |
Every other scenario is classified as a mismatch. This table shows examples of mismatch scenarios:
| Difference (Data Lake/Compass – Application count) | Difference | Difference | Difference |
|---|---|---|---|
|
Checksum verification |
≠ 0 (Incorrect) |
0 (Correct) |
0 (Correct) |
|
Instance count |
0 |
≠ 0 |
0 |
|
Row count |
0 |
0 |
≠ 0 |
|
Classification |
mismatch |
mismatch |
mismatch |