Merge pull request #278 from open-sausages/pulls/3/autosoftcommit

NEW Ensure commits are visible to seachers (fixes #274)
This commit is contained in:
Steve Boyd 2022-05-17 11:39:36 +12:00 committed by GitHub
commit 35c9484f05
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 193 additions and 180 deletions

View File

@ -379,7 +379,7 @@
-->
<autoSoftCommit>
<maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
<maxTime>${solr.autoSoftCommit.maxTime:60000}</maxTime>
</autoSoftCommit>
<!-- Update Related Event Listeners

View File

@ -1,13 +1,26 @@
# Troubleshooting
## Newly indexed content only shows in searches after a delay
First, check how you're running index operations.
In many cases where the `queuedjobs` module is installed,
saving or publishing a record will create a new index job which needs to complete first.
Solr also distinguishes between adding documents to the indexing,
committing them, and making them available to new searches.
In most cases this happens within a few seconds, but
in sometimes it can take up to a minute due to the
`autoSoftCommit` configuration setting defaults in your `solrconfig.xml`.
To find out more detail, read about
[soft vs. hard commits](https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/).
## Common gotchas
* By default number-letter boundaries are treated as a word boundary. For example, `A1` is two words - `a` and `1` - when Solr parses the search term.
* Special characters and operators are not correctly escaped
* Multi-word synonym issues
* When Dolr indexes are reconfigured and reindexed, their content is trashed and rebuilt
* When Solr indexes are reconfigured and reindexed, their content is trashed and rebuilt
### CWP-specific
## CWP-specific
* `solrconfig.xml` customisations fail silently
* Developers arent able to test raw queries or see output via the