Details

    • Type: Improvement Improvement
    • Status: Patch Available
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      In Jackrabbit, there is currently a limitation on how many references (properties referencing to this node) a node can have. The reason is that node references are kept in an in-memory list when getting the references, and also when adding/deleting a reference.

      Proposed solution: Instead of reading/updating/storing the list of references whenever there is a change, use a new class NodeReferencesChanges to keep track of changes where possible.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Patch Available Patch Available
        949d 20h 37m 1 Jukka Zitting 08/Jul/09 10:47
        Jukka Zitting made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Jukka Zitting made changes -
        Workflow jira [ 12391222 ] no-reopen-closed, patch-avail [ 12467941 ]
        Thomas Mueller made changes -
        Field Original Value New Value
        Attachment NodeReferencesChanges.txt [ 12346224 ]
        Hide
        Thomas Mueller added a comment -

        This patch contains a new class NodeReferencesChanges, and the relevant changes in the core components. The persistent manager is not yet changed. This patch does not yet remove the limitation on the number of references per node, but is a first step in this direction. The next steps are to change the NodeReferences class to be disk buffered if the list is too big. Also, the persistent manager interface and implementations should be changed to directly support NodeReferencesChanges or a similar 'delta' mechanism.

        Show
        Thomas Mueller added a comment - This patch contains a new class NodeReferencesChanges, and the relevant changes in the core components. The persistent manager is not yet changed. This patch does not yet remove the limitation on the number of references per node, but is a first step in this direction. The next steps are to change the NodeReferences class to be disk buffered if the list is too big. Also, the persistent manager interface and implementations should be changed to directly support NodeReferencesChanges or a similar 'delta' mechanism.
        Thomas Mueller created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Thomas Mueller
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development