Sequential Counter
- Ben Clark
Overview
Due to the clustered nature of the cache it is not possible to use standard Kettle functionality to create a sequential series of numbers
This step can be used to ensure that next value in a sequence is correctly allocated and reserved for the instance of the rule
Plugin Configuration
Within the plugin:
The following settings can be configured:
Setting | Description |
|---|---|
Server names(s) | The name of the cache server(s) you are using. If the rule is running in DDE then this is automatically be populated and the value will be ignored. |
KeySpace | Tables exist in Keyspace (similar to a database). If the rule is running in DDE then this is automatically be populated with the client name within DDE and the value will be ignored. |
Table | The name of the table which will be created in Cassandra. If left blank this will be the same as the key field name. |
Counter Name | The Cassandra counter field name to write to and read from |
Range Min | The number the counter should start at. e.g. If 10 is entered into the Min range the first entry into the counter table would be 11 |
Range Max | The maximum range the sequence counter number should go up to before erroring. If the maximum counter number is exceed the step will error and sequence will be incremented. The rule should therefore have an error handling step to cater for counters that exceed the maximum range. e.g.  For alternative functionality see Error Code Field |
Output Field | The field to write the next subsequent sequence number to within the rule |
Error Code Field | If “Send To Error Output When Range exceeded” is deselected you can add a Error Code Field. This will automatically populate the chosen field with a value if the Range is exceeded but still allow the row to flow through the step. You can then choose to treat the out of range rows differently in the Rule. |