USE 137 - support JSONLines input#19
Merged
Merged
Conversation
ghukill
commented
Nov 5, 2025
Comment on lines
+226
to
+257
| # read input records from TIMDEX dataset (default) | ||
| # or a JSONLines file | ||
| if input_jsonl: | ||
| with ( | ||
| smart_open.open(input_jsonl, "r") as file_obj, # type: ignore[no-untyped-call] | ||
| jsonlines.Reader(file_obj) as reader, | ||
| ): | ||
| timdex_records = iter(list(reader)) | ||
|
|
||
| else: | ||
| if not dataset_location or not run_id: | ||
| raise click.UsageError( | ||
| "Both '--dataset-location' and '--run-id' are required arguments " | ||
| "when reading input records from the TIMDEX dataset." | ||
| ) | ||
|
|
||
| # init TIMDEXDataset | ||
| timdex_dataset = TIMDEXDataset(dataset_location) | ||
|
|
||
| # query TIMDEX dataset for an iterator of records | ||
| timdex_records = timdex_dataset.read_dicts_iter( | ||
| columns=[ | ||
| "timdex_record_id", | ||
| "run_id", | ||
| "run_record_offset", | ||
| "transformed_record", | ||
| ], | ||
| run_id=run_id, | ||
| where=f"""run_record_offset >= {run_record_offset}""", | ||
| limit=record_limit, | ||
| action="index", | ||
| ) |
Collaborator
Author
There was a problem hiding this comment.
At one point, I think @ehanson8 floated the idea of refactoring this out to a utility function. I considered that again here now that we handle two different possible inputs.
For the time being, I'd propose to keep here as-is, because there are no other known use cases for these inputs getting handled or used. Until then, it feels reasonable that this CLI handles the input + output handling.
Why these changes are being introduced: Initially, the CLI command create-embeddings only supported reading input records from the TIMDEX dataset via TDA. While this is likely the way we'll get input records, supporting a JSONLines file as input is helpful for testing. How this addresses that need: * Adds a new --input-jsonl argument that reads a JSONLines file and uses those rows as input for creating embeddings. * Args --dataset-location and --run-id are required when --input-jsonl is not set. Side effects of this change: * None Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/USE-137
ghukill
force-pushed
the
USE-137-JSONL-input
branch
from
7216c9e to
b898882
Compare
jonavellecuerdo
approved these changes
Nov 7, 2025
jonavellecuerdo
left a comment
jonavellecuerdo
left a comment
Contributor
There was a problem hiding this comment.
Works as expected! ✨
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NOTE: this PR builds on #18. Once the other PR is complete, this PR will get pointed to
mainand merged.Purpose and background context
Small PR to support a JSONLines files as input for the CLI command
create-embeddings.While normally the CLI will read directly from the TIMDEX dataset via TDA, it can be optionally invoked to read records from as JSONLines file that simulates the columns/fields that would come from TDA. This is helpful for testing and will be helpful for ironing out the parallel processing work.
How can a reviewer manually see the effects of these changes?
Set env vars:
If not already done, ensure model is downloaded locally:
Create embeddings with entirely local input + output files:
Note: S3 uris are supported for both
--input-jsonland--ouput-jsonlviasmart_open.Includes new or updated dependencies?
YES:
smart_open[s3]Changes expectations for external applications?
NO
What are the relevant tickets?
Code review