[
https://issues.apache.org/jira/browse/OAK-11930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh updated OAK-11930:
----------------------------
Fix Version/s: 1.86.0
> JCR observation events should not serialize the propertyState for binary
> properties
> -----------------------------------------------------------------------------------
>
> Key: OAK-11930
> URL: https://issues.apache.org/jira/browse/OAK-11930
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Affects Versions: 1.84.0
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
> Fix For: 1.86.0
>
>
> When for an event on a binary property "toString()" is invoked, the current
> implementation always serializes the beforeValue and afterValue, which in the
> case of a binary properties reads and dumps the entire binary property.
> If this happens in the context of a log message, it can end up very large log
> messages (I have a case with hundreds of megabytes); this can lead to OOMs
> and downstream problems in the log processing.
> We should change that behavior; in the case of a binary property toString()
> should not dump the full content of the blobs, but something less
> problematic, for example the blob ids.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
