Skip to content

Commit 08213db

Browse files
Update mendix-data-loader.md
1 parent 8de7507 commit 08213db

1 file changed

Lines changed: 26 additions & 16 deletions

File tree

content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/mendix-data-loader.md

Lines changed: 26 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -98,33 +98,43 @@ To view all ingestion jobs associated with a specific data source in Snowflake,
9898
SELECT * FROM core.ingestion_job WHERE DATASOURCE_ID = '1234abcd' ORDER BY CREATED_DATE_TIME DESC;
9999
```
100100

101-
## Programmatically Trigger an Ingestion From a Mendix App
101+
## Programmatically Triggering an Ingestion Job From a Mendix App
102102

103-
Programmatically triggering an ingestion job can meet data ingestion requirements where a scheduled task may not. This includes cases such as waiting for a last submission to be submitted to a Mendix app before data ingestion occurs. Another example case is to start data ingestion when the load on the Mendix app is the lowest.
103+
Programmatically triggering an ingestion job can meet data ingestion requirements where a scheduled task may not, for example in the following use cases:
104+
105+
* Waiting for a last submission to be submitted to a Mendix app before data ingestion occurs.
106+
* Starting data ingestion when the load on the Mendix app is the lowest.
104107

105108
### Prerequisites
106-
- A fully configured data source in the Mendix Data Loader
107-
- A Mendix app equipped with the Snowflake REST SQL connector
108-
- An authenticated user that is allowed to trigger stored procedures
109109

110-
To trigger an ingestion job programmatically, use the `ExecuteStatement` operation available in the Snowflake REST SQL connector. The statement to be executed has the following syntax.
110+
* A fully configured data source in the Mendix Data Loader
111+
* A Mendix app equipped with the Snowflake REST SQL connector
112+
* An authenticated user that is allowed to trigger stored procedures
113+
114+
### Triggering the Ingestion
115+
116+
To trigger an ingestion job programmatically, use the `ExecuteStatement` operation available in the Snowflake REST SQL connector.
117+
118+
1. Obtain the Snowflake data source ID by performing the following steps:
119+
120+
1. In the Snowflake environment, open the Mendix Data Loader by clicking **Data Products** > **Apps** > **Mendix Data Loader**.
121+
2. Open the application by clicking the `MENDIX_DATA_LOADER` tab.
122+
3. Click **View** by the configured data source.
123+
4. Copy the value for the `ID` key.
124+
125+
2. In the Snowflake REST SQL connector, use the `ExecuteStatement` operation to execute the following statement:
111126

112127
```sql
113128
CALL {NAME_OF_THE_MENDIX_DATA_LOADER}.MX_FUNCTIONS.RUN_INGESTION_JOB('{DATASOURCE_ID}','{TASK_ID}');
114129
```
115130

116-
- The default name for the Mendix Data Loader is `MENDIX_DATA_LOADER`
117-
- Data source ID is a required parameter
118-
- Task ID is an optional parameter
131+
where you must specify the following variables:
119132

120-
To find the data source ID for a given data source:
121-
1. Navigate to the Snowflake environment
122-
2. Open the Mendix Data Loader; Data Products -> Apps -> Mendix Data Loader
123-
3. Open the application by clicking the `MENDIX_DATA_LOADER` tab
124-
4. Click *View* on the configured data source
125-
5. Copy the value for the `ID` key
133+
* `{NAME_OF_THE_MENDIX_DATA_LOADER}` - The default name for the Mendix Data Loader is `MENDIX_DATA_LOADER`
134+
* `{DATASOURCE_ID}` - Required; the data source ID that you obtained in step 1
135+
* `{TASK_ID}` - Optional
126136

127-
For a data source with the ID *40FJYP9D*, the resulting statement will be.
137+
For example, for a data source with the ID *40FJYP9D*, the resulting statement would be:
128138

129139
```sql
130140
CALL MENDIX_DATA_LOADER.MX_FUNCTIONS.RUN_INGESTION_JOB('40FJYP9D','');

0 commit comments

Comments
 (0)