You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/09/18 15:55:44 UTC
[jira] Created: (JCR-1741) Flush volatile index when size limit is
reached
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.
[jira] Updated: (JCR-1741) Flush volatile index when size limit is
reached
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-1741:
----------------------------------
Attachment: JCR-1741.patch
Proposed patch.
> 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
> Attachments: JCR-1741.patch
>
>
> 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.
[jira] Resolved: (JCR-1741) Flush volatile index when size limit is
reached
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1741.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Committed patch in revision: 706697
> 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
> Fix For: 1.6.0
>
> Attachments: JCR-1741.patch
>
>
> 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.