If you want to reproduce a problem event that has occurred, or re-check summary analysis results, you re-execute queries by reloading the data for a specific time period.
To re-execute queries, you use the sdptplput command. For the target data to be re-processed, use information about the input tuples collected in the tuple log file. When you execute the command, tuples are reloaded to the input stream queues from the tuple information collected in the tuple log file. After reloading of tuples is completed, the putEnd method is executed on all input stream queues, and the query group is initialized.
You can check the result of query re-execution by using the sdptplls command to display the tuple information collected from the output stream queue to the tuple log.
The following figure shows the flow of data when queries are re-executed to check execution results.
Figure 4-2 Flow of data during query re-execution
The following subsections discuss the permitted range of query re-execution, query re-execution procedure, and notes about re-executing queries.
The permitted range of query re-execution differs between the server mode and the data source mode. The permitted range is as follows:
For details about the timestamp adjustment function, see 10.8 Timestamp adjustment for tuples.
You use a tuple log file that has been acquired to re-execute a query. A query can be re-executed in an environment that is different from the environment used to acquire the tuple logs, except that the default character encoding must be the same in both environments.
This example assumes that the environment in which queries are re-executed is different from the environment where tuple logs were acquired.
To re-execute queries:
For details about the sdpcql, sdpcqlstart, sdptplput, and sdptplls commands, see sdpcql (registers a query group), sdpcqlstart (starts a query group), sdptplput (reloads tuples), and sdptplls (displays tuple information) in 7. Commands.