When an event store is used by any app, a database is created with its tables depending on the type of process we have used in the application. The database for development and production are created separately. If you want to have a look at these tables and their data, you can check it within the syntasa application by navigating to DataStores>>DataSets tab.
Here are the steps to go to the 'DataSets' screen:
- Go to Resources>>DataStores
- Select the DataStore of type Event Store that has been used by any app for both Dev and Prod
- Click on the tab icon 'DataSets' from the left side menu.
In the screenshot above, you'll notice two sections displayed for datasets: one for development and the other for production. Since no app has utilized this event store in any of its processes yet, both the development and production are shown without any tables. However, once an app initiates a process, tables will be generated, and they will appear in the respective lists. Let's try to understand it with an example below:
In the screenshot above, you'll notice several datasets listed under Development. This occurrence is due to the utilization of the event store by the 'AA Loader' app process for the development workflow. Typically, these datasets are prefixed with the application's key value ('demoapp_eventstores' in the provided screenshot). Once the application employs the event store for the production workflow, you can expect datasets to appear under Production as well.
DataSets Details
When you click any dataset from the left side, you will see four tabs for each dataset:
- Details & Schema
- Preview
- State
- Usage
1. Details & Schema
This screen provides fundamental details regarding the dataset, including its schema. You'll find information such as the dataset type, file type, name, partition scheme, database name, and more. The schema section displays all column names, their types, and their order within the table.
Additionally, it indicates which column contains partition information. Typically, partitioning is performed on a single column, so you'll observe only one column with the partitioned value marked as 'Yes,' while the rest will be marked as 'No.'
2. Preview
The 'Preview' tab shows the content of the selected dataset.
At the top right corner of the table, you'll find the total row count and the last modified date of the dataset displayed. Additionally, you have the option to download the entire table data as a CSV file by clicking on the download icon located at the top right of the table.
3. State
On the 'State' tab, you can review the size and count of the data that was fetched into the dataset at specific times. The 'State' tab displays the following five columns:
- Date: This column displays the date when the data was fetched, based on the partition pattern.
- Hour: If the data is partitioned hourly, this column shows the corresponding hour values.
- Count: Indicates the number of records fetched and stored.
- Size: Reflects the total size of the stored data.
- Modified Date: Shows the timestamp indicating when the data was fetched and stored.
You have the option to download the entire table data as a CSV file by clicking on the download icon located at the top right of the table.
4. Usage
This tab displays the components that utilize the selected dataset. Below is the description for each column:
- Component: Indicates the component using the selected dataset. For instance, 'App'.
- Name: Specifies the name of the component utilizing the dataset. For example, 'EventStoreApp' is the app name associated with the 'App' component.
- Environment: Denotes the environment name in which the component uses the dataset.
- Available Action: Lists permitted actions such as reading, writing, etc.
Similar to the 'Preview' and 'State' tabs, you get the option to download the entire table data as a CSV file by clicking on the download icon located at the top right of the table.