pdfs as parquet text #2
Open
Conversation
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
stefaneng
approved these changes
Nov 3, 2025
Member
stefaneng
left a comment
stefaneng
left a comment
There was a problem hiding this comment.
Cool idea! Looks good to me
stefaneng
reviewed
Nov 3, 2025
Member
There was a problem hiding this comment.
Curious why this one is 10.3 MB? is this all of the current documents?
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.
I think we can store the texts of all the pdfs we have ever seen as a directory of parquet files with structure
sha256 | dateprocessed | text(list-of-strings)This directory can be the basis for the other parsing pipelines. I think we can actually store that parquet directory right here in the repo, making it maximally transparent and allowing easy reproducibility for the rest of our stuff.