[ 
https://jira.nuxeo.com/browse/NXCM-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=96464#comment-96464
 ] 

Mariana Cedica commented on NXCM-336:
-------------------------------------

Done with : 
http://hg.nuxeo.org/addons/nuxeo-platform-document-routing/rev/d18c14628866
The number of comments is stored now also on the 
"info_comments:numberOfComments" property, available if the 
"CommentsInfoHolder" facet is put on a document.
By default this is implemented to be used on the documents of type 
DocumentRouteStep. Since this document type has no extra schema ( except for 
dublicore) , the solution was to add this property in a new schema , even if in 
terms of performance this implies an extra join in the query when fetching the 
document.

A listener is updating this property each time a comment is added or deleted on 
the document.
For the existing documents the "Document.Routing.UpdateCommentsInfoOnDocument" 
operation was added . It allows to synchronise the number of comments on the 
document with the numeber of comments obtained using the commentManager.
The chain can be invoked by from nuxeo-shell with :
run updateCommentsOnDoc

> Avoid fetching all the comments each time we display the route
> --------------------------------------------------------------
>
>                 Key: NXCM-336
>                 URL: https://jira.nuxeo.com/browse/NXCM-336
>             Project: Nuxeo Case Management
>          Issue Type: Improvement
>    Affects Versions: 1.7
>            Reporter: Mariana Cedica
>            Priority: Critical
>             Fix For: 1.7.1
>
>
> Fetching all the comments each time the route page is displayed has an impact 
> on the performance. See NXCM-325 for bench results.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to