[hibernate-issues] [Hibernate-JIRA] Resolved: (HSEARCH-220) introduce session.flushToIndexes API and deprecate batch_size

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard resolved HSEARCH-220.
--------------------------------------

    Resolution: Fixed

Needs documentation

> introduce session.flushToIndexes API and deprecate batch_size
> -------------------------------------------------------------
>
>                 Key: HSEARCH-220
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-220
>             Project: Hibernate Search
>          Issue Type: New Feature
>          Components: engine
>            Reporter: Emmanuel Bernard
>             Fix For: 3.1.0
>
>
> hibernate.search.worker.batch_size has many drawbacks
>  - the value is not accessible programatically hence error prone
>  - it applies to any operations regardless of mass indexing
>  - it is used 99% of the time in close conjunction with a % and session.clear()
>  - the side effect is quite big as the index is "transactionally" committed
> To replace it, I introduced 
> session.flushToIndexes();
> this method manually triggers changes in queue. It does not trigger an hibernate core flush().
> This seems more reasonable and will make the code safer.
> WDYT?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira