com.apama.config
Event AutoPurgeStore


Wrapper for MemoryStoreConfigurationStore which will automatically purge it's rows depending on the parameters passed into it.

It will automatically add a "timestamp" field to the schema and automatically populate this field when a row is added or updated.

The possible purge parameters can be:-

MAX_ROWS - Will only keep a maximum number of rows, deleting the oldest riw when a new row is added that goes over the limit. TIMEOUT - Will periodically remove rows older than the timeout. Used in conjunction with the PURGE_INTERVAL or PURGE_TIME parameters. PURGE_INTERVAL - This is the interval in seconds on when to purge rows older than TIMEOUT. PURGE_TIME - This is the clock time in the format "hh:mm:ss" on when to purge rows older than TIMEOUT.

By default there is no automatic purging. Multiple purging parameters can be used, for example, you can set the MAX_ROWS and the TIMEOUT/PURGE_INTERVAL paramters to only keep a set number of rows, but also puge rows older than TIMEOUT every PURGE_INTERVAL.
See Also:
com.apama.config.AutoPurgeTableConstants - 
com.apama.config.MemoryStoreConfigurationStore - 
com.apama.config.ConfigurationStoreInterface - 

Action summary
 voidcreateTable(integer id, com.apama.config.Schema schema, action<integer, com.apama.config.ConfigurationTableInterface> onSuccess, action<integer, string> onError)

Copy of createTable() from MemoryStoreConfigurationStore to ensure our getTable() is called.
 
Action detail

createTable

            void createTable(integer id, com.apama.config.Schema schema, action<integer, com.apama.config.ConfigurationTableInterface> onSuccess, action<integer, string> onError)
        
Copy of createTable() from MemoryStoreConfigurationStore to ensure our getTable() is called.
Parameters:
id - The request identifier.
schema - The schema for the new table.
onSuccess - Action to be called when the new table is successfully created. The id passed to the callback will be the same as the id argument to the #createTable() call and the configTable argument will provide access to the new table.
onError - Action to be called if the new table cannot be created. The id passed to the callback will be the same as the id argument to the #createTable() call and the message argument will provide a human- readable description of the failure.