Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | Tools - Import Tool |
| Version | 14.0 |
|
442 B
|
|
69 KB
There are two limitations of Cassandra that cause the incorrect count reported in the Import Tool.
1. INSERT behaves like UPSERT (see issue #9016). In this test case, there are duplicate records, but Cassandra doesn't report any error for the INSERT operation. Therefore, the Import Tool thinks that all the records are inserted successfully.
2. The Statement.getUpdateCount() method is not implemented in the Cassandra JDBC driver (see issue #9208). So, we can't use the getUpdateCount method to try to get an accurate inserted count.
Issue #9689 |
| Closed |
| Won't Fix |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
relates to #9021
Issue #9021Import: batch mode - final row count shown in the status field might be incorrect |
There are two limitations of Cassandra that cause the incorrect count reported in the Import Tool.
1. INSERT behaves like UPSERT (see issue #9016). In this test case, there are duplicate records, but Cassandra doesn't report any error for the INSERT operation. Therefore, the Import Tool thinks that all the records are inserted successfully.
2. The Statement.getUpdateCount() method is not implemented in the Cassandra JDBC driver (see issue #9208). So, we can't use the getUpdateCount method to try to get an accurate inserted count.