You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/07/03 13:39:00 UTC
[jira] [Created] (JCRVLT-308) Simple File Aggregate should only
update content in repo in case the actual binary has been changed (or some
metadata)
Konrad Windszus created JCRVLT-308:
--------------------------------------
Summary: Simple File Aggregate should only update content in repo in case the actual binary has been changed (or some metadata)
Key: JCRVLT-308
URL: https://issues.apache.org/jira/browse/JCRVLT-308
Project: Jackrabbit FileVault
Issue Type: Bug
Components: vlt
Affects Versions: 3.1.44
Reporter: Konrad Windszus
Usually for aggregates the nodes/properties are actually only written if they differ between the To-Be state given in the package and the As-Is state in the repository. That mechanism does not work though for simple file aggregates. Those are always overwritten in the repository (because at least their jcr:lastModification property is touched every time).
Instead the simple file aggregate should be compared based on the checksum with the binary from the repository. Only in case they differ or metadata is explicitly written/removed as well the node should actually be touched.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)