Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix rds writer process and with more typing #217

Merged
merged 1 commit into from
Jan 5, 2024
Merged

Conversation

mzappitello
Copy link
Contributor

The RDS writer process waits for items to be put on a metadata queue, pops them off, and then writes that file to the metadata. In the past, the queue was typed with any, as it was being populated with an obscure pyarrow object we couldn't deduce properly.

With the recent changes to how we write parquet files, these changed to strings. This caused the process to fail since it was attempting to pull a path attribute out a string, causing an uncaught exception.

I've updated the process to expect a string from the queue and put in typing hints that should prevent an error like this in the future.

Asana Task: https://app.asana.com/0/1205827492903547/1206288301107382/f

The RDS writer process waits for items to be put on a metadata queue,
pops them off, and then writes that file to the metadata. In the past,
the queue was typed with any, as it was being populated with an obscure
pyarrow object we couldn't deduce properly.

With the recent changes to how we write parquet files, these changed to
strings. This caused the process to fail since it was attempting to pull
a `path` attribute out a string, causing an uncaught exception.

I've updated the process to expect a string from the queue and put in
typing hints that should prevent an error like this in the future.
Copy link
Collaborator

@rymarczy rymarczy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

I turned off ingestion on staging and updated the metadatalog RDS table with all of the parquet paths that were written since the last manual update I did.

Should be good to deploy and kick everything back on. On PROD, I can reconcile the parquet file and metadatalog table diffs later today and write up an SQL query for the infra team to run against the PROD rds.

@mzappitello mzappitello merged commit 7dd25a3 into main Jan 5, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants