Click on this icon at the top-right corner of a container, for overflow menu.
Click to configure the visualization (e.g. Pie, Bar, Line etc.) of this container.
Reuse mode of a container defines if this container can receive the data generated by another operation.
Different reuse modes are:
Never: In Never mode, the container will not store the data generated by the new operation.
Replace: In Replace mode, container’s data will be replaced by the new data generated by any operation. New Data must be of the same DST (Data Set Type)
Append Unique: This mode will ensure that the new data will get Appended to the existing records. Append Unique ensures that only unique records (as per the Primary key of the DST) are retained. A new record with the primary key of an existing record overwrites the old record.
Append All: This mode will ensure that the new data will get Appended to the existing records. Append All mode ensures all the new records are appended to the existing set of records, irrespective of the primary key. So, for e.g. if a new record with the primary key of an existing record is inserted then both old and new records are retained.
|Note: Append All mode lets you harvest data in Klera.|
An Exploration has as a series of operations. When you run any operation manually, it kicks off a chain of operations in that series to re-run. The execution mode of a container defines when operation(s) in this container should be re-run, depending upon the previous operation in the series.
On Operation Complete: The operation(s) of the container will be re-run only when the previous operation is complete. This is the default execution mode.
|Note: It is highly recommended to use this mode unless the use case calls for one of the below:|
On Data Update: The operation(s) of the container are re-run on every data update of the previous operation. The previous operation may generate data in multiple chunks during its complete run and on each of these chunks, the container’s operation(s) will be re-run. This is a very expensive mode of operation execution (resource-wise) and must be used prudently.
On Interval: The operation(s) of the container are re-run on a regular interval. The previous operation may be a long one and generate data in multiple chunks. This option lets you set a refresh frequency of the operation irrespective of the data frequency. This is an expensive mode of execution and must be used prudently. Please note that once the previous operation completes, this container’s operation(s) will definitely run even if the interval has not expired yet.
Use this option to manually re-run the operations of the container. It will re-run the complete chain of operations, starting from this container onwards. The user will not be prompted to provide values as the operations will be run with input values from the previous run.
When you want to change the values of input parameters at the time of re-run, then click on “Re-Execute Interactively” option. Please note that this option will re-run the complete chain of operations starting from this container onwards and prompt the user for input by providing a form.
Shows the details of the operation(s) of this container. Details include Operation Name, User who ran the operation, Parameters etc.
You will also get the following options on the overflow menu.
You can raise an alert when a certain data threshold is breached. Please refer to Alert and Triggers for details.
This will permanently delete the container and its visualization(s). Please note that this option does not delete the data and its associated operations from the Exploration. It is just a visual element that is being deleted. Hence, when the Exploration is re-run, all the operation(s) associated with the data of this container will also be re-run.
Shows the last time when the data was updated in this container.