PhixFlow Help

Sequence

Overview

Use the sequence properties to set up a sequence of unique numbers that you want to allocate to records in a stream. 

To create a sequence, specify a start value and a block size. The block size specifies how often you go back to the database to update the number up to which you have allocated. This is referred to as the 'tidemark'. PhixFlow then allocates those numbers from the database and stores them in memory. When PhixFlow reserves a block, it marks the last reserved value in the database. 

To assign a number from memory to stream records, use the nextValue function in an expression. You can also find the last assigned number using the curValue function. When all the numbers in the sequence have been used, the next time the nextValue function is called PhixFlow reserves the next block of numbers before assigning the next value. 

Sections on this page

It is much quicker for PhixFlow to assign a number from memory than it is to assign a number from the database. It also takes time to reserve the next block of numbers.

Gaps in the Number Sequence

Sequence numbers are unique, but there may be gaps between sequence numbers. This depends on:

  • the block size specified when the sequence is set up
  • unexpected server shut-down.

Server shut-down clears any remaining numbers from memory. When the server restarts, PhixFlow reserves a new block from the last reserved value. This can leave a gap between:

  • the last number allocated before PhixFlow was shut down
  • and the first number allocated after PhixFlow is restarted.

For example,

  1. You create a sequence with a block size of 100. It has the values 0-99.
  2. You have allocated the numbers 1 to 50 from memory.
  3. PhixFlow shuts down.
  4. On restart, PhixFlow reserves a new block from 100 to 199.
  5. PhixFlow starts issuing numbers from memory, starting with 100. 
  6. The numbers from 51 to 99 will never be issued.

Block Size and Performance 

Use the block size to specify the range of values in the sequence. The block size affects PhixFlow performance.

  • A very small block size increases the number of times that PhixFlow has to go to the database to reserve another block.  This slows down performance.
  • A very large block size increases the risk that PhixFlow is shut down with unallocated numbers in memory.  

We recommend you set a large block size, to optimise performance.

If you require a continuous sequence of values for items:

  • in a small stream set, you may want to accept the overhead of assigning every value in the sequence from the database. In this case, set the Block Size to 1.
  • in larger stream sets, consider an alternative method of assigning the value.

Sequence Properties

To create a sequence, in the repository, right-click Sequences and click  Add.

For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties.  For a full list of all the PhixFlow property tabs and windows, see Property Tabs.

Basic Settings

FieldDescription
NameEnter the name of the sequence.
Start ValueEnter the first value in the sequence.
Block Size

Enter a number to set the size of the sequence of numbers. This will depend on the number of records in the stream set to which you are allocating unique numbers. For example, if the stream set has 10,000 records, the block size should be at least 10,000.

Sequences provide unique numbers, but they the numbers may not always be contiguous.

Block size has an effect on performance; see Block Size and Performance, above.

Current ValuePhixFlow displays the highest value already allocated.

Example: Using a Sequence

To set a stream attribute to a unique order ID:

  1. Create a sequence and set its Name to order_id.
  2. Create a stream with an Integer attribute.

  3. Set its attribute expression to: 
      nextValue('order_id')

  4. Every time a new record is generated in this stream, nextValue will return a new unique value for the attribute.


Please let us know if we could improve this page feedback@phixflow.com