You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2008/11/20 15:30:46 UTC

[jira] Created: (JCR-1870) jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read

jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read
-----------------------------------------------------------------------

                 Key: JCR-1870
                 URL: https://issues.apache.org/jira/browse/JCR-1870
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-jcr2spi
            Reporter: angela


issue reported by stefan:

upon reloading of an invalidated node, jcr2spi doesn't use batch-read but only retrieves the NodeInfo.

basically, WorkspaceItemStateFactory ll 92 needs to be changed to omit the extra handling of 
invalidated node entries and always use RepositoryService.getItemInfos when build the NodeState.

i will try it out as soon as possible.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (JCR-1870) jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read

Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig resolved JCR-1870.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.5

Fixed at revision 766748  


> jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read
> -----------------------------------------------------------------------
>
>                 Key: JCR-1870
>                 URL: https://issues.apache.org/jira/browse/JCR-1870
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 1.5.0
>            Reporter: angela
>            Assignee: Michael Dürig
>             Fix For: 1.5.5, 1.6.0
>
>
> issue reported by stefan:
> upon reloading of an invalidated node, jcr2spi doesn't use batch-read but only retrieves the NodeInfo.
> basically, WorkspaceItemStateFactory ll 92 needs to be changed to omit the extra handling of 
> invalidated node entries and always use RepositoryService.getItemInfos when build the NodeState.
> i will try it out as soon as possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-1870) jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1870:
-------------------------------

    Fix Version/s:     (was: 1.6.0)

> jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read
> -----------------------------------------------------------------------
>
>                 Key: JCR-1870
>                 URL: https://issues.apache.org/jira/browse/JCR-1870
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 1.5.0
>            Reporter: angela
>            Assignee: Michael Dürig
>             Fix For: 1.5.5
>
>
> issue reported by stefan:
> upon reloading of an invalidated node, jcr2spi doesn't use batch-read but only retrieves the NodeInfo.
> basically, WorkspaceItemStateFactory ll 92 needs to be changed to omit the extra handling of 
> invalidated node entries and always use RepositoryService.getItemInfos when build the NodeState.
> i will try it out as soon as possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (JCR-1870) jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read

Posted by "angela (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-1870.
-------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0
         Assignee: angela

> jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read
> -----------------------------------------------------------------------
>
>                 Key: JCR-1870
>                 URL: https://issues.apache.org/jira/browse/JCR-1870
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.6.0
>
>
> issue reported by stefan:
> upon reloading of an invalidated node, jcr2spi doesn't use batch-read but only retrieves the NodeInfo.
> basically, WorkspaceItemStateFactory ll 92 needs to be changed to omit the extra handling of 
> invalidated node entries and always use RepositoryService.getItemInfos when build the NodeState.
> i will try it out as soon as possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-1870) jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read

Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated JCR-1870:
-------------------------------

    Affects Version/s: 1.5.0

> jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read
> -----------------------------------------------------------------------
>
>                 Key: JCR-1870
>                 URL: https://issues.apache.org/jira/browse/JCR-1870
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 1.5.0
>            Reporter: angela
>            Assignee: Michael Dürig
>             Fix For: 1.6.0
>
>
> issue reported by stefan:
> upon reloading of an invalidated node, jcr2spi doesn't use batch-read but only retrieves the NodeInfo.
> basically, WorkspaceItemStateFactory ll 92 needs to be changed to omit the extra handling of 
> invalidated node entries and always use RepositoryService.getItemInfos when build the NodeState.
> i will try it out as soon as possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (JCR-1870) jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read

Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig reopened JCR-1870:
--------------------------------

      Assignee: Michael Dürig  (was: angela)

Reopening for 1.5.0

> jcr2spi: reloading of invalidated nodes doesn't benefit from batch-read
> -----------------------------------------------------------------------
>
>                 Key: JCR-1870
>                 URL: https://issues.apache.org/jira/browse/JCR-1870
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 1.5.0
>            Reporter: angela
>            Assignee: Michael Dürig
>             Fix For: 1.6.0
>
>
> issue reported by stefan:
> upon reloading of an invalidated node, jcr2spi doesn't use batch-read but only retrieves the NodeInfo.
> basically, WorkspaceItemStateFactory ll 92 needs to be changed to omit the extra handling of 
> invalidated node entries and always use RepositoryService.getItemInfos when build the NodeState.
> i will try it out as soon as possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.