Allow text search to be disabled #354
Comments
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Mar 21, 2024
This introduces a new system property, `conversation.search.index-enabled`, that, when set to 'false', disables the full-text search functionality and corresponding indexing tasks. Disabling this functionality can save some resources on instances that do not use the feature, and have a large amount of messages in their database.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Mar 21, 2024
This introduces a new system property, `conversation.search.index-enabled`, that, when set to 'false', disables the full-text search functionality and corresponding indexing tasks. Disabling this functionality can save some resources on instances that do not use the feature, and have a large amount of messages in their database.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Mar 21, 2024
This introduces a new system property, `conversation.search.index-enabled`, that, when set to 'false', disables the full-text search functionality and corresponding indexing tasks. Disabling this functionality can save some resources on instances that do not use the feature, and have a large amount of messages in their database.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Text search is based on Lucene indices. These indices take resources to generate. That is typically a negligible amount, but for very large amounts of data, this can add up (eg: Ignite's 10.5 million records take about 7 minutes to be fully indexed).
If text search is not used, then this is a waste of resources. A configuration option should be added to disable this functionality.
The text was updated successfully, but these errors were encountered: