-
Bug
-
Resolution: Done
-
Major
-
4.6.0.Final
-
None
When jcr:data property of nt:resource is set with the same value it already has, the property changed event is fired despite of there is no change. Probably this wrong behavior affects all BINARY properties, nor only the jar:data.
- is caused by
-
MODE-1856 No-op mutations seems to trigger indexing updates
- Closed