Streams and Time Periods
In any given moment, a streams contains a set of records. This is the record-set. You can set the time period over which PhixFlow collects records. The period can be:
For non-transactional periods, PhixFlow checks for incomplete record-sets and reports an error if it finds them. However, pipes from transactional streams allow incomplete record-sets, as data is constantly changing.
Publishing Streams
When you make changes to a stream's properties or its attributes, PhixFlow publishes the changes to the PhixFlow database. This happens automatically in the background. Publishing many streams or streams with many attributes can take some time, and may slow performance.
If the stream properties are set incorrectly, PhixFlow will not be able to publish the stream to the database. If this happens, the System Console will report the publishing error. PhixFlow will also display an error message if you try to interact with the stream, for example to view its data or to run analysis. You must correct the stream properties, so that PhixFlow can retry publishing the stream.
During the publishing process, PhixFlow may create temporary streams in its database. These are kept for a period, then automatically removed when a system task runs. For information about:
- the system task, see Using Tasks and Task Plans
- configuring the period that temporary streams are kept; see System Configuration → Delete Temp Streams after Days.
To ensure that PhixFlow can publish data changes, its database must have enough space to hold a copy of the largest table. For the different databases, the space needs to be in:
- Oracle: temporary table space
- SQL Server: temporary file group
- MySQL: the file system.