3b6e1123b8
Sorting by primary key before inserting data into DB is fixed. Earlier we were sorting input slice of BucketBandwidthRollup but then we were putting all entries into map to rollup input data. Iteration over map with a range loop doesn't guarantee any specific order so we were loosing sorted order when we were creating with this map slices to use with DB insert. New code is also using map but when map is full its sorting map keys separately and iterates over them to get data from map. https://github.com/storj/storj/issues/5332 Change-Id: I5bf09489b0eecb6858bf854ab387b660124bf53f |
||
|---|---|---|
| .. | ||
| encryptionkey_test.go | ||
| encryptionkey.go | ||
| endpoint_test.go | ||
| endpoint.go | ||
| orders_test.go | ||
| rollups_chore.go | ||
| rollups_write_cache_test.go | ||
| rollups_write_cache.go | ||
| service_test.go | ||
| service.go | ||
| signer_test.go | ||
| signer.go | ||
| window_endpoint_phase.go | ||