hibernate batch insert - how flush works?

Question

I need to insert a lot of data in a database using hibernate, i was looking at batch insert from hibernate, what i am using is similar to the example on the manual:

Session session = sessionFactory.openSession();
Transaction tx = session.beginTransaction();

for ( int i=0; i<100000; i++ ) {
    Customer customer = new Customer(.....);
    session.save(customer);
    if ( i % 20 == 0 ) { //20, same as the JDBC batch size
        //flush a batch of inserts and release memory:
        session.flush();
        session.clear();
    }
}

tx.commit();
session.close();

but i see that flush doesn't write the data on the database. Reading about it, if the code is inside a transaction then nothing will be committed to the database until the transaction performs a commit.

So what is the need to use flush/clear ? seems useless, if the data are not written on the database then they are in memory.

How can i force hibernate to write data in the database?

Thanks

JB Nizet · Accepted Answer · 2011-11-29 12:09:06Z

5

The data is sent to the database, and is not in memory anymore. It's just not made definitively persistent until the transaction commit. It's exacltly the same as if you executes the following sequences of statements in any database tool:

begin;
insert into ...
insert into ...
insert into ...
// here, three inserts have been done on the database. But they will only be made
// definitively persistent at commit time
...
commit;

The flush consists in executing the insert statements.

The commit consists in executing the commit statement.

answered Nov 29, 2011 at 12:09

JB Nizet

694k94 gold badges1.3k silver badges1.3k bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Ralph · Accepted Answer · 2011-11-29 12:06:55Z

1

The data will be written to the database, but according to the transaction isolation level you will not see them (in other transactions) until the transaction is committed.

Use some sql statement logger, that prints the statmentes that are transported over the database connection, then you will see that the statmentes are send to the database.

answered Nov 29, 2011 at 12:06

Ralph

121k57 gold badges300 silver badges391 bronze badges

Comments

Konstantin Pribluda · Accepted Answer · 2011-11-29 12:26:22Z

1

For best perfromance you also have to commit transactions. Flushing and clearing session clears hibernate caches, but data is moved to JDBC connection caches, and is still uncommited ( different RDBMS / drivers show differrent behaviour ) - you are just shifting proble to other place without real improvements in perfromance.

answered Nov 29, 2011 at 12:26

Konstantin Pribluda

12.3k1 gold badge33 silver badges38 bronze badges

Comments

Santosh · Accepted Answer · 2011-11-29 13:26:45Z

1

Having flush() at the location mentioned saves you memory too as your session will be cleared regularly. Otherwise you will have 100000 object in memory and might run out of memory for larger count. Check out this article.

answered Nov 29, 2011 at 13:26

Santosh

18k4 gold badges58 silver badges80 bronze badges

Collectives™ on Stack Overflow

hibernate batch insert - how flush works?

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related