com.atlassian.confluence.pages.collab.impl

Class DefaultSynchronyDataService

java.lang.Object

com.atlassian.confluence.pages.collab.impl.DefaultSynchronyDataService

All Implemented Interfaces:

SynchronyDataService

public class DefaultSynchronyDataService
extends Object
implements SynchronyDataService

Since:

7.0.0

Constructor Summary

Constructors

Constructor and Description
DefaultSynchronyDataService(SynchronyLockManager lockManager, SynchronyEvictionDao evictionDao, SynchronyEvictionProgressTracking progressTracking)

Method Summary

Modifier and Type	Method and Description
SynchronyRowsCount	currentSynchronyDatasetSize(Long contentId) If the parameter is not null, returns size of Synchrony history for that entity.
void	hardRemoveHistoryOlderThan(int thresholdHours) Remove all events from content entities, which have any data older than .
void	removeApplicationCredentials(String applicationId) Remove application credentials from Synchrony tables
void	softRemoveHistoryOlderThan(int thresholdHours, int contentCount) Remove approximately content records from Synchrony history, which are older than and are safe for removal.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

DefaultSynchronyDataService

public DefaultSynchronyDataService(SynchronyLockManager lockManager,
                                   SynchronyEvictionDao evictionDao,
                                   SynchronyEvictionProgressTracking progressTracking)

Method Detail

currentSynchronyDatasetSize

public SynchronyRowsCount currentSynchronyDatasetSize(Long contentId)

Description copied from interface: SynchronyDataService

If the parameter is not null, returns size of Synchrony history for that entity. If the parameter is null, returns overall Synchrony rows count for the whole instance.

Specified by:

currentSynchronyDatasetSize in interface SynchronyDataService

softRemoveHistoryOlderThan

public void softRemoveHistoryOlderThan(int thresholdHours,
                                       int contentCount)

Description copied from interface: SynchronyDataService

Remove approximately content records from Synchrony history, which are older than and are safe for removal. Execution of this method should avoid any bad effect on users experience because we touch here only content which haven't been updated for hours. This method provides only 'best effort' guarantee for data removal. Deletion strategy depends on the implementation details of how exactly do we determine that content hasn't been touched in and might change. In some edge cases the method will not remove any data. If you're looking for a guaranteed way to clean synchrony history, please look at SynchronyDataService.hardRemoveHistoryOlderThan(int).

The main purpose of this method is disk space cleanup in collab editing tables. Parameter allows to shift trade-off between removal efficiency (disk reclaiming) and the degree of intrusiveness.

The method is executed synchronously in the same thread. If exception is thrown somewhere in the middle, it is possible to have only a part of data removed, because the removal might happen in several transactions, but remaining data will always stay consistent (e.g. synchrony data consistent with content properties).

Specified by:

softRemoveHistoryOlderThan in interface SynchronyDataService

hardRemoveHistoryOlderThan

public void hardRemoveHistoryOlderThan(int thresholdHours)

Description copied from interface: SynchronyDataService

Remove all events from content entities, which have any data older than . Theoretically this might cause last 30 seconds of history disappear. This method is designed to be called rarely and be the last resort for GDPR compliance.

The method guarantees to remove old personal data in order to be compliant with regulations. If the customer doesn't care about any regulations, it shouldn't generally call the method, instead less intrusive SynchronyDataService.softRemoveHistoryOlderThan(int, int) should be used.

The method is executed synchronously in the same thread. If exception is thrown somewhere in the middle, it is possible to have only a part of data removed, because the removal might happen in several transactions, but remaining data will always stay consistent (e.g. synchrony data consistent with content properties).

Specified by:

hardRemoveHistoryOlderThan in interface SynchronyDataService

removeApplicationCredentials

public void removeApplicationCredentials(String applicationId)

Description copied from interface: SynchronyDataService

Remove application credentials from Synchrony tables

Specified by:

removeApplicationCredentials in interface SynchronyDataService

Parameters:

applicationId - if of application to remove