Skip to content

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.

2 participants