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

Allow plugins to define their own caches' attributes

XMLWordPrintable

    • 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.

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

      It is possible for plugins to do an expensive per-Confluence startup calculation and store the data in the cache. If the plugin can keep the data updated throughout the lifecycle, it would a disadvantage if that calculated data is wiped away automatically every hour.

      It would be nice if the plugin could tell the caching system:

      "For cache XYZ, don't ever automatically invalidate anything in it"

            [CONFSERVER-22493] Allow plugins to define their own caches' attributes

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3569956 ] New: JAC Suggestion Workflow 3 [ 4324569 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3175373 ] New: JAC Suggestion Workflow 4 [ 3569956 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3032612 ] New: JAC Suggestion Workflow 2 [ 3175373 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2534141 ] New: JAC Suggestion Workflow [ 3032612 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2294426 ] New: Confluence Workflow - Public Facing v4 [ 2534141 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2189367 ] New: Confluence Workflow - Public Facing v3 [ 2294426 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1919817 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2189367 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1753032 ] New: Confluence Workflow - Public Facing v3 [ 1919817 ]
            jonah (Inactive) made changes -
            Description Original: It is possible for plugins to do an expensive per-Confluence startup calculation and store the data in the cache. If the plugin can keep the data updated throughout the lifecycle, it would a disadvantage if that calculated data is wiped away automatically every hour.

            It would be nice if the plugin could tell the caching system:

            "For cache XYZ, don't ever automatically invalidate anything in it"             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-22493].
              {panel}

            It is possible for plugins to do an expensive per-Confluence startup calculation and store the data in the cache. If the plugin can keep the data updated throughout the lifecycle, it would a disadvantage if that calculated data is wiped away automatically every hour.

            It would be nice if the plugin could tell the caching system:

            "For cache XYZ, don't ever automatically invalidate anything in it"
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-22493 [ CONFCLOUD-22493 ]

              Unassigned Unassigned
              dchui DavidA
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: