Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.8.18
-
12
-
Severity 2 - Major
-
30
-
Description
When indexing larger attachments, it would benefit our clients greatly if we checked the size of attachment before indexing same. In other words, when an attachment is too large, instead of attempting the indexing, bail earlier if the attachment is too large.
System property atlassian.indexing.contentbody.maxsize is meant to provide this functionality, however has been reported not to be working.
Workaround
As of 5.9 there is 'canary' functionality in the Office Connector that will abort indexing on large documents if they would cause an OutOfMemory error. More details can be found here.
NB: The canary is now enabled by default and does not require a dark feature.
Attachments
Issue Links
- Discovered while testing
-
CONFSERVER-40493 Add a system property for a max index size for PDF
- Closed
- is related to
-
CONFSERVER-39462 Skip Context Extraction for large indexes when file exceeds max config setting
- Closed
- relates to
-
CONFSERVER-40176 Confluence ignores the system property officeconnector.textextract.word.docxmaxsize
- Gathering Impact
- is blocked by
-
PSR-52 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...