<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Plus it seems the default value is compound = true, just like in Lucene. This is not what we are saying in the doc.<div><br></div><div>Am I completely off-base?</div><div><br><div><div>On Nov 12, 2008, at 17:59, Emmanuel Bernard wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Actually I sat down and read more about compound file format.<div>Basically, instead of creating several files representing a single segment, the compound format creates a single file for the whole segment.</div><div>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.</div><div><br></div><div>Compounds Pro:</div><div> - less file handlers</div><div><br></div><div>Compounds Con:</div><div> - slower at indexing</div><div> - takes temporarily more space on disk as the uncompound segment is converted to a compound segment when done</div><div><br></div><div>I don't think this affects the incremental copy so much are segments are essentially read-only.</div><div><br></div><div>I believe this is not the story we tell to people in the doc, so we need to fix that.</div><div><br><div><div>On Nov 11, 2008, at 10:07, Emmanuel Bernard wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It seems that a few parameters should not be configurable per transaction|batch<div> - use_compound_file</div><div> - <span class="Apple-style-span" style="border-collapse: collapse; font-family: 'Courier New'; ">max_field_length? not sure</span></div><div><font class="Apple-style-span" face="'Courier New'"><span class="Apple-style-span" style="border-collapse: collapse;"> - term_index_interval (is that a config influencing IndexReader?) </span></font></div><!--StartFragment--><div><br></div><div>What do you think?</div><div>I am a bit worried to stick them as is in the project / book as they are right now.</div><div><br></div><div>Let's try and sort this out today.</div></div>_______________________________________________<br>hibernate-dev mailing list<br><a href="mailto:hibernate-dev@lists.jboss.org">hibernate-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/hibernate-dev">https://lists.jboss.org/mailman/listinfo/hibernate-dev</a><br></blockquote></div><br></div></div>_______________________________________________<br>hibernate-dev mailing list<br><a href="mailto:hibernate-dev@lists.jboss.org">hibernate-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/hibernate-dev<br></blockquote></div><br></div></body></html>