-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 10.10-HF52
-
Component/s: BlobManager, Bulk
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #43, nxplatform #44, nxplatform #45
-
Story Points:1
There are cases where the content/length (size of the main blob) is not set, for instance after a custom mass import or maybe when using direct S3 upload.
Accessing the content/length is going to access the blob to get its size, this means downloading the blob when the blob is stored in S3.
This is a known bottleneck during reindexing.
A workaround is to update the content/length to -1 at the database level
but it is better to have a specific procedure to populate this field with a correct value.
This could be a Bulk Action searching for a document with a blob and an empty or unset (-1) document/length.
Ideally, the value is set without downloading the blob and without triggering any listener (like a system property update).
This approach is better than having an option to avoid downloading the blob during indexing: NXP-30543.
- is related to
-
NXP-30624 Make s3SetBlobLength (previously s3SetContentLength) bulk action more reliable
- Resolved
-
NXP-30543 Have an option to prevent blob fetching during indexing
- Resolved
-
NXP-32330 Make S3SetBlobLengthAction work with S3BlobProvider
- Resolved
- is required by
-
NXP-30931 Add DownloadBlobGuard to VCS
- Resolved
- Is referenced in