From 377b2843baf6f80f4c10f6aaa0f4b3a8b7f7c79c Mon Sep 17 00:00:00 2001 From: Evan Owens Date: Sat, 5 Apr 2014 07:12:16 +1000 Subject: [PATCH] Fix documentation about `immediate` Unless I misimplemented this, "immediate" means persist to ElasticSearch "immediately"; before flushing. Default behavior is false; persist to ElasticSearch postFlush. --- Resources/doc/types.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Resources/doc/types.md b/Resources/doc/types.md index 38fa045..e01b5ae 100644 --- a/Resources/doc/types.md +++ b/Resources/doc/types.md @@ -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 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` -option on a type persistence configuration to false. +option on a type persistence configuration to `true`. ```yaml persistence: - immediate: false + immediate: true ```