Introduce preference to disable fulltext indexing#8478
Merged
Conversation
Siedlerchr
reviewed
Jan 31, 2022
| <Button fx:id="autolinkRegexHelp"/> | ||
| </HBox> | ||
|
|
||
| <Label styleClass="sectionHeader" text="%Fulltext-Index linked files"/> |
Member
There was a problem hiding this comment.
I would just name the section header "Fulltext Index"
Member
|
lgtm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fulltext indexing can take up lots of resources on big libraries. This PR introduces a preference to disable it.

This is particularly important if JabRef struggles to determine if a linked file was updated since it was indexed (e.g. when using a library on a shared network drive without 'modified' timestamps)
Fixes #8468
CHANGELOG.mddescribed in a way that is understandable for the average user (if applicable)