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

bugfix: Point out use of Tags db and how it works #4109

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

stchris
Copy link
Contributor

@stchris stchris commented Jan 24, 2025

ingest-file uses the Tags functionality from servicelayer to cache certain document types during ingest to speed up its operation. Normally the settings file defaults to trying the ALEPH_DATABASE_URI followed by the FTM_STORE_URI, which in most cases should be set to non-default values.

But if one were to just follow our prod environment docs blindly and not uncomment these two settings then the TAGS_DATABASE_URI would be unset, causing servicelayer to pick the default (sqlite:///) which breaks now that we have multiple threads writing to the tags database.

This change documents how this setting works and encourages one to set it if the above two settings are left to defaults.

Relates to #4002, #3816

ingest-file uses the Tags functionality from servicelayer to cache certain document types
during ingest to speed up its operation. Normally the settings file defaults to trying
the ALEPH_DATABASE_URI followed by the FTM_STORE_URI, which in most cases should be set
to non-default values.

But if one were to just follow our prod environment docs blindly and not uncomment these
two settings then the TAGS_DATABASE_URI would be unset, causing servicelayer to pick the
default (sqlite:///) which breaks now that we have multiple threads writing to the tags
database.

This change documents how this setting works and encourages one to set it if the above
two settings are left to defaults.

Relates to #4002, #3816
@stchris stchris merged commit 238a8ff into main Jan 24, 2025
3 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.

1 participant