-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2023.0
-
Component/s: BlobManager, Core
-
Release Notes Summary:org.nuxeo.ecm.core.blob.LocalBlobProvider is now the default binary manager
-
Tags:
-
Team:PLATFORM
-
Story Points:1
Today, the default blob provider implementation is org.nuxeo.ecm.core.blob.binary.DefaultBinaryManager defined by:
nuxeo.core.binarymanager=org.nuxeo.ecm.core.blob.binary.DefaultBinaryManager
in common-base/nuxeo.defaults
which is a rather old and obsolete impl compared to LocalBlobProvider.java
Moreover, the new Full GC impl (NXP-28565) does not handle DefaultBinaryManager whereas LocalBlobStore is supported.
Should we take the opportunity to make LocalBlobProvider the default blob provider for 2023?
Out of the box, are the binaries/blobs stored the same way with both DefaultBinaryManager and LocalBlobProvider implementation, that a 2021 -> 2023 upgrade goes through seamlessly? According to NXP-28276 yes. On the contrary, it means projects upgrading from 2021 to 2023 will have to set back explicitly:
nuxeo.core.binarymanager=org.nuxeo.ecm.core.blob.binary.DefaultBinaryManager
in their nuxeo.conf
- is related to
-
NXP-28276 Refactor blob providers infrastructure for more flexibility
- Resolved
-
NXP-28565 Make orphan binaries GC scalable
- Resolved
-
NXP-32331 Usage of URLBlob leaves the file:content length null when using BlobProvider
- Resolved
-
NXDOC-2588 Update File Storage page
- Resolved
-
NXP-32044 Make BlobProvider specification the default binary manager
- Resolved