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

Sanne Grinovero (JIRA) noreply at atlassian.com
Fri Nov 21 11:52:18 EST 2008


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

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

I just realised this is going to break
the indexing examples in the book.
To refresh your memory: your examples recommended to use

purgeAll
optimize
on scrollable {
  index entity
}
optimize

and I had added a flushToIndexes in this way:

purgeall
flushToIndexes
optimize
on scrollable {
  index entity
}
optimize

to be sure to optimize AFTER the purge (and immediately after).
If you "cancel" the first optimization by fixing this as described
this tip to optimize is not good anymore (it would work, but the tip is about
using less disk space).
this issue is requiring to "shuffle" the order of operations as requested
by the code, I don't think this is a good idea.. why would a developer
issue more than one optimization anyway?

I think the issue should be changed, so to not apply automatic optimizations
during batch operations (disable the mod counter): we should not remove an explicitly requested
"manual operation", or mess with the position of it in the queue.

> 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