Added documentation for ignoring missing hits
This commit is contained in:
parent
00b67fd8a4
commit
c05e0caa9c
1 changed files with 17 additions and 0 deletions
17
README.md
17
README.md
|
|
@ -534,6 +534,23 @@ The delete listener disregards the callback.
|
||||||
|
|
||||||
> **Propel** doesn't support this feature yet.
|
> **Propel** doesn't support this feature yet.
|
||||||
|
|
||||||
|
### Ignoring missing index results
|
||||||
|
|
||||||
|
By default, FOSElasticaBundle will throw an exception if the results returned from
|
||||||
|
Elasticsearch are different from the results it finds from the chosen persistence
|
||||||
|
provider. This may pose problems for a large index where updates do not occur instantly
|
||||||
|
or another process has removed the results from your persistence provider without
|
||||||
|
updating Elasticsearch.
|
||||||
|
|
||||||
|
The error you're likely to see is something like:
|
||||||
|
'Cannot find corresponding Doctrine objects for all Elastica results.'
|
||||||
|
|
||||||
|
To solve this issue, each mapped object can be configured to ignore the missing results:
|
||||||
|
|
||||||
|
persistence:
|
||||||
|
elastica_to_model_transformer:
|
||||||
|
ignore_missing: true
|
||||||
|
|
||||||
### Advanced elasticsearch configuration
|
### Advanced elasticsearch configuration
|
||||||
|
|
||||||
Any setting can be specified when declaring a type. For example, to enable a custom analyzer, you could write:
|
Any setting can be specified when declaring a type. For example, to enable a custom analyzer, you could write:
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue