Commit 51a35ac
committed
Move read ordering back to SQL query
Why these changes are being introduced:
The ordering of metadata records by filename + run_record_offset was moved
into the python pandas context for a performance boost, but it was not ideal
from the POV of keeping the majority of our logic in SQL.
Upon learning that we could use `hash(filename)` to still order the filenames
but with a dramatic speed and memory improvement, it makes sense to move this
back into the SQL context.
How this addresses that need:
* Moves metadata query ordering back to SQL instead of python pandas context
Side effects of this change:
* None
Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/TIMX-5431 parent 14c2b1b commit 51a35ac
2 files changed
+9
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
387 | 387 | | |
388 | 388 | | |
389 | 389 | | |
390 | | - | |
391 | 390 | | |
392 | 391 | | |
393 | 392 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
15 | | - | |
| 15 | + | |
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
| |||
642 | 642 | | |
643 | 643 | | |
644 | 644 | | |
| 645 | + | |
| 646 | + | |
| 647 | + | |
| 648 | + | |
| 649 | + | |
| 650 | + | |
| 651 | + | |
| 652 | + | |
645 | 653 | | |
646 | 654 | | |
647 | 655 | | |
| |||
0 commit comments