-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
For the sake of:
- Performance
- Troubleshooting
- Indexing bugs
...It can be desirable to have an option to not index the contents of any attachments in Confluence. Our current process to disable attachment index via disabling a number of extractors is an okay workaround, but does not disable indexing of ALL attachments. Text/HTML/XML files are still indexed and cannot be disabled via the UI. This presents problems since the Lucene upgrade in Confluence 5.2 introduces new bugs can hang the entire indexing process such as:
However, even if the bugs (and other future Lucene bugs that may arise) are fixed, one may wish to forgo attachment indexing for the sake of improving Confluence performance.
This request is to add an option in the UI to simply disable all attachment contents. The permanent equivalent of issuing a POST request http://<confluence_url>/rest/prototype/latest/index/reindex
with Content-Type: application/json and form data option = CONTENT_ONLY.
- is incorporated by
-
CONFSERVER-39462 Skip Context Extraction for large indexes when file exceeds max config setting
- Closed
- is related to
-
CONFSERVER-32566 Indexing job becomes stuck due to the UAX29URLEmailTokenizerImpl analyzer
-
- Closed
-
- relates to
-
CONFCLOUD-32752 Option in the UI to disable all attachment content indexing in Confluence
- Closed
- mentioned in
[CONFSERVER-32752] Option in the UI to disable all attachment content indexing in Confluence
Workflow | Original: JAC Suggestion Workflow 4 [ 3562895 ] | New: JAC Suggestion Workflow 3 [ 4330956 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3183988 ] | New: JAC Suggestion Workflow 4 [ 3562895 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3027341 ] | New: JAC Suggestion Workflow 2 [ 3183988 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2529935 ] | New: JAC Suggestion Workflow [ 3027341 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2260266 ] | New: Confluence Workflow - Public Facing v4 [ 2529935 ] |
Fix Version/s | New: 6.2.2 [ 72292 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is incorporated by |
Status | Original: Needs Verification [ 10004 ] | New: Open [ 1 ] |
Remote Link | New: This issue links to "Page (Bulldog)" [ 295036 ] |
We have now completed a range of work relating to how we index attachments.
Please review how attachments are indexed for full details.
Whilst we have not implemented a UI for changing the limit on attachment indexing, we have introduced a new system property atlassian.indexing.attachment.maxsize (default 100MB) which defines if an uploaded file is larger than the limit set by this property, text extraction and indexing will be skipped.
Setting this parameter to 0 will effectively stop attempting to index any attachments.