[hibernate-issues] [Hibernate-JIRA] Created: (HSEARCH-300) Fix documentation on use_compound_file

[Emmanuel Bernard (JIRA)]

Fix documentation on use_compound_file
--------------------------------------

                 Key: HSEARCH-300
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-300
             Project: Hibernate Search
          Issue Type: Bug
          Components: documentation
            Reporter: Emmanuel Bernard
             Fix For: 3.1.0.CR1


hibernate.search.[indexname].indexwriter.use_compound_file (no tx/batch)

Actually I sat down and read more about compound file format.
Basically, instead of creating several files representing a single segment, the compound format creates a single file for the whole segment.
And you can have a mix of compound and non compound segments for a given index. So you can set different settings for transactional and batch in theory. Not sure why though.

Compounds Pro:
 - less file handlers

Compounds Con:
 - slower at indexing
 - takes temporarily more space on disk as the uncompound segment is converted to a compound segment when done

I don't think this affects the incremental copy so much are segments are essentially read-only.

I believe this is not the story we tell to people in the doc, so we need to fix that.

Plus it seems the default value is compound = true, just like in Lucene. This is not what we are saying in the doc.



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