Flush volatile index when size limit is reached
-----------------------------------------------
Key: JCR-1741
URL: https://issues.apache.org/jira/browse/JCR-1741
Project: Jackrabbit
Issue Type: Improvement
Components: jackrabbit-core
Reporter: Marcel Reutegger
Priority: Minor
Currently the volatile index is committed when minMergeDocs is reached. This is
inconvenient because it does not take the size of nodes into account account.
When lots of small nodes are added the volatile index should be committed less
frequently. Similarly when nodes with lots of properties are indexed the
volatile index should be committed more frequently.
Instead the size of the volatile index in bytes should trigger a disk write.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
