Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-39462

Skip Context Extraction for large indexes when file exceeds max config setting

    XMLWordPrintable

Details

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      You can configure the maximum indexable size of an attachment - https://confluence.atlassian.com/conf57/configuring-attachment-size-701435663.html

      However, the way this works is that the content is still all extracted and then simply not saved in the index.

      Customers often use this setting because large documents are resource intensive to extract the content from and often fail. With the current implementation we're helping to not store the content, but we're still expending resources to extract the content.

      Recommend that this setting be modified so that these files are excluded earlier in the process and not extracted at all.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jvirgil Jay Virgil
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: