[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-246) Run optimize at the end of the transaction even if flushToIndexes() is used
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Sun Oct 26 20:31:04 EDT 2008
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31537#action_31537 ]
Emmanuel Bernard commented on HSEARCH-246:
------------------------------------------
I doubt it is fixed.
flushToIndexes() process the whole queue including optimize operations. which means it could be executed multiple times per batch.
> 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
More information about the hibernate-issues
mailing list