[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-246) Run optimize at the end of the transaction even if flushToIndexes() is used

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31799#action_31799 ] 

Sanne Grinovero commented on HSEARCH-246:
-----------------------------------------

what about avoiding to trigger automatic optimization when at least one LuceneWork had batch=true ?
It would not be really linked to flushToIndexes() but to the index( entity ); still I think this could server the purpose
of disabling this behaviour during indexing, and avoid breaking any interface.


> Run optimize at the end of the transaction even if flushToIndexes() is used
> ---------------------------------------------------------------------------
>
>                 Key: HSEARCH-246
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-246
>             Project: Hibernate Search
>          Issue Type: Improvement
>          Components: optimizer
>            Reporter: Emmanuel Bernard
>             Fix For: 3.1.0
>
>
> I am not sure if it's easily feasible but it should be the case. I am mentioning as the feature in the book for now.

-- 
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