[Hippo-cms7-user] Bypass versioning of the document when updating property of node
Frank van Lankvelt
f.vanlankvelt at 1hippo.com
Sun Apr 15 07:44:41 CEST 2012
On 14 apr. 2012, at 21:39, RM <rmilin at gmail.com> wrote:
> Thanks guys for previous answers,
> I'm using hippo version 7.7.1. and have one more question :)
> I want the information to be stored in a document- how many times the
> document has been viewed in hst.
This sounds like a bad idea to me; even when only doing it in batches, this will increase the number of write operations (reindexation, journal entries) significantly.
Could you take a look at the google analytics addon? It displays data collected by GA in the context if a document. Other analytics engines could be supported in a similar manner, though I'm not aware of any examples.
The big advantage is that such specialised analytics solutions are optimized for writing log data. Whereas the content repository and the hst have been optimized for reading / rendering content.
> The problem is that I don't want to update the document in a component
> through workflow (getWorkflowPersistenceManager()), because a new version of
> document on every increment of the property is created.
> According to:
> Ard -> The console does not involve workflow.
> Even when I tried the following actions [ check out / changed property views
> / check in ] on the document, in the console, the new version of document
> has been created. So even if I skip workflow the version is created.
Yeah, you'll need to skip the check-in part to not get new versions.
> What is the right way to bypass versioning of the document and update only
> the property of node in component that extends BaseHstComponent?
> View this message in context: http://hippo.2275632.n2.nabble.com/Bypass-versioning-of-the-document-when-updating-property-of-node-tp7466379p7466379.html
> Sent from the Hippo CMS 7 mailing list archive at Nabble.com.
> Hippo-cms7-user mailing list and forums
More information about the Hippo-cms7-user