HSEARCH-3075 Document discard changes on transaction rollback

hibernate · Aug 9, 2019 · 45ec4ef · 45ec4ef
1 parent 6ae163d
commit 45ec4ef
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/documentation/src/main/asciidoc/mapper-orm-indexing-automatic.asciidoc b/documentation/src/main/asciidoc/mapper-orm-indexing-automatic.asciidoc
@@ -37,7 +37,8 @@ This is because queries are executed on the database side,
 One workaround is to <<mapper-orm-indexing-explicit,explicitly reindex>> after you run such queries.
 Indexing happens after transactions are committed::
 Indexes are not updated immediately, but only after transactions are successfully committed.
-That way, if a transaction is rolled back, the indexes will be left in a state consistent with the database.
+That way, if a transaction is rolled back, the indexes will be left in a state consistent with the database,
+discarding all the index changes that were planned during the transaction.
 +
 This means in particular that Hibernate Search will retrieve the state of entities after the transaction is committed.
 As a result, clearing the session during the transaction may cause trouble: