Hi Alexander, can you open a new JIRA issue and provide a test case for the problem you are experiencing. The problem seems different than the one described here.

There is a problem with DocumentBuilder, getDocument method. It uses "entity.getClass()" instead of "Hibernate.getClass(entity)", thus resulting document has "_hibernate_class" field value equal to hibernate proxy class, not entity class. No search could be performed later on such an index, since search injects criteria "_hibernate_class:Entity".

The code does not lose the last row. I have it working in the test suite

FullTextSession s = Search.createFullTextSession( openSession() );
Transaction tx = s.beginTransaction();
int loop = 14;
for (int i = 0; i < loop; i++) {
s.connection().createStatement().executeUpdate( "insert into Email(id, title, body, header) values( + "
+ ( i + 1 ) + ", 'Bob Sponge', 'Meet the guys who create the software', 'nope')" );
}
tx.commit();
s.close();

//check non created object does get found!!1
s = new FullTextSessionImpl( openSession() );
tx = s.beginTransaction();
ScrollableResults results = s.createCriteria( Email.class ).scroll( ScrollMode.FORWARD_ONLY );
int index = 0;
while ( results.next() ) {
index++;
s.index( results.get( 0 ) );
if ( index % 5 == 0 ) s.clear();
}
tx.commit();
s.clear();
tx = s.beginTransaction();
QueryParser parser = new QueryParser( "id", new StopAnalyzer() );
List result = s.createFullTextQuery( parser.parse( "body:create" ) ).list();
assertEquals( 14, result.size() );
for (Object object : result) {
s.delete( object );
}
tx.commit();
s.close();

I am using this as a workaround, seems to be smarter anyway because it doesn't trigger the sequential selects:

ScrollableResults cursor = session.createQuery("select o from " + entityClass.getName() + " o fetch all properties").scroll();

Documentation example is also wrong for batching (yeah it is also wrong in the H3 reference docs), the batch misses the last row:

transaction = fullTextSession.beginTransaction();
//Scrollable results will avoid loading too many objects in memory
ScrollableResults results = fullTextSession.createCriteria( Email.class ).scroll( ScrollMode.FORWARD_ONLY );
int index = 0;
while( results.next() ) {
index++;
fullTextSession.index( results.get(0) ); //index each element
if (index % batchSize == 0) s.clear(); //clear every batchSize since the queue is processed
}
transaction.commit();

Should be:

transaction = fullTextSession.beginTransaction();
//Scrollable results will avoid loading too many objects in memory
ScrollableResults results = fullTextSession.createCriteria( Email.class ).scroll( ScrollMode.FORWARD_ONLY );
int index = 0;
while( true ) {
index++;
fullTextSession.index( results.get(0) ); //index each element
if (index % batchSize == 0) s.clear(); //clear every batchSize since the queue is processed

if (results.isLast())
break;
else
results.next();
}
transaction.commit();