Fix documentation about immediate
Unless I misimplemented this, "immediate" means persist to ElasticSearch "immediately"; before flushing. Default behavior is false; persist to ElasticSearch postFlush.
This commit is contained in:
parent
d67d525b66
commit
377b2843ba
|
@ -270,9 +270,9 @@ FOSElasticaBundle, since 3.0.0 performs its indexing in the postFlush Doctrine e
|
||||||
instead of prePersist and preUpdate which means that indexing will only occur when there
|
instead of prePersist and preUpdate which means that indexing will only occur when there
|
||||||
has been a successful flush. This new default makes more sense but in the instance where
|
has been a successful flush. This new default makes more sense but in the instance where
|
||||||
you want to perform indexing before the flush is confirmed you may set the `immediate`
|
you want to perform indexing before the flush is confirmed you may set the `immediate`
|
||||||
option on a type persistence configuration to false.
|
option on a type persistence configuration to `true`.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
persistence:
|
persistence:
|
||||||
immediate: false
|
immediate: true
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in a new issue