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

[BREAKING] fix: 🐛 quick fix to avoid mongodb errors with big rows #201

Merged
merged 2 commits into from
Apr 7, 2022

Conversation

severo
Copy link
Collaborator

@severo severo commented Apr 6, 2022

if a row is too big to be inserted in the cache database, we just store
the empty string for each of its cells, and mark it as erroneous. All
the cells are marked as truncated in the /rows endpoints. See
#197.

This commit also contains the first migration script, with instructions
to apply and write them, fixing #200

BREAKING: the cache database structure has changed. Apply the migration
script: 20220406_cache_dbrow_status_and_since.py

if a row is too big to be inserted in the cache database, we just store
the empty string for each of its cells, and mark it as erroneous. All
the cells are marked as truncated in the /rows endpoints. See
#197.

This commit also contains the first migration script, with instructions
to apply and write them.

BREAKING: the cache database structure has changed. Apply the migration
script: 20220406_cache_dbrow_status_and_since.py
@severo severo changed the title fix: 🐛 quick fix to avoid mongodb errors with big rows [BREAKING] fix: 🐛 quick fix to avoid mongodb errors with big rows Apr 6, 2022
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.

1 participant