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

(#112, #114) Save search metadata as a separate document. #113

Merged
merged 2 commits into from
Jan 28, 2025

Conversation

blairlearn
Copy link
Contributor

@blairlearn blairlearn commented Jan 22, 2025

Closes #112
Closes #114

@blairlearn blairlearn changed the base branch from develop to release/v2.0.0 January 23, 2025 17:09
@blairlearn blairlearn changed the title (#112) Save search metadata as a separate document. (#112, #114) Save search metadata as a separate document. Jan 23, 2025
Copy link
Member

@bryanpizzillo bryanpizzillo left a comment

Choose a reason for hiding this comment

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

I am approving, but monitoring the logging for this application will be REALLY important to determine how often the 2 files don't get saved together. There should also be some AWS response codes that could allow a retry of one of the failed files being uploaded.

I assume a failure of one of the files will end up being a failure from the API, so a user would not be sent a bad cache item. But it will be good to know the frequency and have access to these logs.

Maybe OpenTelementry is something that should be looked into to capture this info in DataDog.

@blairlearn blairlearn merged commit 9805285 into release/v2.0.0 Jan 28, 2025
2 checks passed
@blairlearn blairlearn deleted the ticket/112-metadata branch January 28, 2025 20:10
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.

Cannot store large amounts of metadata
2 participants