Groovy updaters fail due to incorrect resultFetchSize configuration

This has to do with the batch size in the Groovy updater in combination with org.apache.jackrabbit.core.query.lucene.QueryResultImpl.LazyScoreNodeIteratorImpl#fetchNext and org.apache.jackrabbit.core.query.lucene.QueryResultImpl#getResults which reexecutes the query at the beginning of a new batch and skips the amount of results it already iterated over. However after the groovy updater batch a session save happens and these changes will be persisted and lucene indexes will be updated. Now the second time the query happens the first N items will not be in the result set of the query anymore (maybe somebody searches for a property and the property has been removed in the meantime). This causes the skip to skip over the resulting items.