- Navigate to
Change the configurations within the
<analytics-data-purging>property as shown below.
Code Block language xml
<analytics-data-purging> <!-- Below entry will indicate purging is enable or not. If user wants to enable data purging for cluster then this property need to be enable in all nodes --> <purging-enable>true</purging-enable> <cron-expression>0 0 12 * * ?</cron-expression> <!-- Tables that need include to purging. Use regex expression to specify the table name that need include to purging.--> <purge-include-tables> <table>.*</table> <!--<table>.*jmx.*</table>--> </purge-include-tables> <!-- All records that insert before the specified retention time will be eligible to purge --> <data-retention-days>365</data-retention-days> </analytics-data-purging>
The properties of the above configuration file are shown below.
Change the value to true if you want to enable data purging.
The cron expression to define how you want to schedule the data purging operation. For example, the following cron expression will configure the archive job to run at 12:00 PM (noon) every day :
0 0 12 * * ?For more information on cron expressions, go to Oracle Documentation.
Specify the tables of which you want to purge data. By default, it is configured to perform data purging on all tables as follows:
<table>.*</table>However, you can specify the required tables by defining a regular expression or a table name within the
<table>property. Define one tag per each regular expression if you want to specify multiple tables.
Define the value as to keep data of only the last 'n' no of days back in the selected table. For example, the default value 365 will purge all data stored before 1 year.