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

contentbylabel macro should use index not db

    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

      Right now, the contentbylabel macro isn't quite as efficient as it could be – it goes through the LabelManager to do stuff that would be faster in Lucene. This is especially an issue now that looking for labela AND labelb in the macro will load all content with either label, then do the join.

      Which raises the question of whether the LabelManager should do those things in Lucene too, so we separate interface from implementation.

      Attachments

        Issue Links

          duplicates

          Suggestion - CONFSERVER-8865 Improve content-by-label macro performance

          • Closed
          relates to

          Suggestion - CONFSERVER-4969 contentbylabel macro should support AND condition

          • Closed
          was cloned as

          Suggestion - CONFSERVER-8399 Deprecate "operator" parameter of contentbylabel macro

          • Closed

          Activity

            People

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: