On this page
Configure SQL for Confluence
After upgrading or installing Cache for Confluence, to navigate to the Global Configuration page:
- Log in as a user with the System Administrator Global Permission.
- Enter Cache in the Search box on the top corner of the page.
- Select Cache from the resulted list of options. The Global Configuration page is displayed.
OR
- Log in as a user with the System Administrator Global Permission.
- Select Add-ons from the Administration menu (cog icon:
) at the top right corner of your screen. - Scroll down to Bob Swift Configuration on the left sidebar.
- Select Cache Configuration.
Global Configuration
This configuration page contains global settings that control the behavior of the Cache for Confluence app, more specifically, cache settings for the Cache and Future macros. Once saved, settings are immediately applied to any macros in use. Refer to the following image:
Table: Configuration options explained
| Option | Default | Description |
|---|---|---|
| Default Retry | Disabled | When enabled, the Cache macro will recognize when a rendering indicates an error that can be retried. The cache macro will try to render previously cached data, if available, instead of the error and will retry on the next cache render request. |
| Default Retry Interval | 15 | This is the time in seconds that the Future macro will wait, by default, to retry rendering contents. It corresponds to the 'retryInterval' parameter. |
| Load Text Option | Title | Text that is to be displayed by the future macro while content is still being rendered to the page. Select "Title" to display the title parameter value set with the macro. Select "Text and Title" to display the default load text prefixed by the title parameter value. The following options are available for selection:
|
| Maximum Number of Entries | 1000 | This is the number of cache entries that will be kept. Entries above this value will force the older entries to be removed. |
| Maximum Cache Size | 100 | Total amount of data (in Megabytes) that will be kept in the cache. Entries added that cause the total size to be exceeded this value then force the removal of older entries. This setting directly impacts JVM memory use. |
| Help us improve the product | ON | As part of building awesome apps we sometime need to gather some basic data to continually improve. This app collects and sends some very basic data for us to process. No private user data or personally identifiable information is sent. view the documentation for more details on what is being sent. |
