1
93%
main: 93%

Ran 25 Aug 2025 08:33PM UTC

Files 7

Run time 0s

Badge

Embed ▾

Committed 25 Aug 2025 08:25PM UTC coverage: 92.989% (-0.08%) from 93.071%

Job # 17219998053.1

Build Type

Pull #168

github

Committed by

ghukill

Commit Message

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-543

Pull Request Pull Request #168: TIMX 543 - Optimize current records metadata queries and data retreival

Run Details

504 of 542 relevant lines covered (92.99%)

0.93 hits per line

MITLibraries / timdex-dataset-api / 17219998053 / 1
93%
main: 93%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 17219998053.1

MITLibraries / timdex-dataset-api / 17219998053 / 1 93% main: 93%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 17219998053.1

MITLibraries / timdex-dataset-api / 17219998053 / 1
93%
main: 93%

README BADGES
x