• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? 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"

          Form Name

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

            Confluence 5.5 has shipped a new Cache API which allows for more control over any cache you create.

            It's not a great idea to have a cache that never expires, but if you need something like this, the new cache api will allow you to set a large expiry time.

            I will close the issue as Obsolete assuming this new API covers this use case, feel free to reopen if it does now.

            m@ (Inactive) added a comment - Confluence 5.5 has shipped a new Cache API which allows for more control over any cache you create. It's not a great idea to have a cache that never expires, but if you need something like this, the new cache api will allow you to set a large expiry time. I will close the issue as Obsolete assuming this new API covers this use case, feel free to reopen if it does now.

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

                Created:
                Updated:
                Resolved: