Better handling for Repository Messages
---------------------------------------
Key: NXP-1933
URL: http://jira.nuxeo.org/browse/NXP-1933
Project: Nuxeo Enterprise Platform 5
Issue Type: Improvement
Components: Core, Query / Search
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.1.3
Depending on the way the core API is used, creating a document can result in
several Messages (Created/Modified).
When theses messages are used to trigger sync or async indexing they create
unuseful load : like indexing twice the same document.
This is particularly bad when triggering async processing that are done in
seperated thread : it creates deadlocks.
We should clean up a little this part :
- drop sync indexing messages when DM is not populated
- make duplicated messages as duplicated and let listener service choose if
the message needs to be processed
=> the search service does not need to process 2 indexing event on the same
doc in the same transaction
=> audit service may choose to log all events
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
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
