Closed
Description
User 1
- Simple table structure id primary key -> json map
- Tests do not fail with no concurrency.
- Tests fail with concurrency with table not found error
- Java, Spring framework to accept http requests and perform backend logic, (Hibernate is used for some metadata tables), JDBC for connecting to dolt: most queries are issued using JDBC directly (e.g., JdbcTemplate::query or JdbcTemplate::execute)
- Both read and write queries (e.g., checking if an element is already in the DB before inserting)
- A single table is used where the elements are stored. We also have a metadata table that maps commit ids in our system to dolt commit hashes. This is updated once per commit. In our failing tests, ~5000 commits were issued with different changes (new elements, modifications, deleting elements).
- dolt commits are used (see above); the metadata table is stored on a separate dolt branch (but commits are not created in this metadata branch, it is only used to separate real data from our metadata), dolt features are used via SQL functions (e.g., CALL dolt_commit(...);)
User 2
- Used mydumper to dump a large database
- Using default myloader configuration that uses 4 threads to load.
- myloader fails with table not found error. Different table each time.
Activity