[
https://issues.apache.org/jira/browse/JCR-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-832:
------------------------------
Fix Version/s: (was: 1.3.2)
This seems more complex than expected. There is already an existing "remove
property" code path based on BLOBFileValue.remove(), but that doesn't work
correctly for database persistence with externalBLOBs set to false because the
BLOBFileValue.remove() call ends up removing the temporary copy of the value
instead of the actual database row.
Instead of adding a new code path for handling database persistence, I'd rather
have a way that hooks the required functionality to the existing code path.
Also, this issue might get obsoleted with the new data store feature.
Thus, I'm removing this issue from the 1.3.2 roadmap.
> BundleDBPersistenceManager does not free blobStore resources
> ------------------------------------------------------------
>
> Key: JCR-832
> URL: https://issues.apache.org/jira/browse/JCR-832
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.3, 1.3.1
> Reporter: Przemo Pakulski
> Assignee: Tobias Bocanegra
> Attachments: JCR-832-patch.txt
>
>
> When removing binary property from node or removing node containing binary
> property, resources occupied by binary property are not freed (orphaned
> records remains in associated ${schemaObjectPrefix}BINVAL table).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
