[ https://issues.apache.org/jira/browse/JCR-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-3277. -------------------------------- Resolution: Fixed Fix Version/s: (was: 2.7) This will go out in Jackrabbit 2.6.0 so resolving as fixed. Let's use follow-up issues for possible further enhancements. PS. Note that the improved consistency checker seems to have uncovered some problem in the way concurrent imports are handled. See JCR-3504. > Let consistency report provide more information > ----------------------------------------------- > > Key: JCR-3277 > URL: https://issues.apache.org/jira/browse/JCR-3277 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Reporter: Unico Hommes > Assignee: Unico Hommes > Fix For: 2.6 > > Attachments: morereportinfo.patch > > > Currently the consistency report items only contain a node id and a message > string. I see the following use cases benefit from more information: > - allow callers of the consistency checker to do postprocessing of nodes such > as putting extra information on a fixed node > - allow callers of the consistency checker to do custom reporting with > statistics on type of inconsistencies and other information such as number > and id of virtual nodes > - inconsistencies typically involve two node ids: a subject and an object > node (for instance orphaned nodes have a node id but also the id of the > parent that is no longer present) > I created a patch that enhances the consistency report items with the > following information: > - aside from node id (the subject of the report item) also an object node id > - each report item has an event type, such as 'abandoned', 'orphaned', etc. > - report items also report root nodes and virtual nodes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira