| description |
|---|
Technical documentation detailing migration steps |
This specifies the migration steps which are specific to the payment index.
Step 1: Adding a target index - Add index name dss-payment_v2 as below:
In kibana, dev tools, apply the below command
PUT dss-payment_v2 {} // add mapping file content here. mapping.json as attached below |
{% hint style="info" %} Note: This name should be as the value present in ingest es.index.namemapping.json24 May 2021, 11:15 AM {% endhint %}
Step 2: Optional changes required in Ingest application properties
Ingest pipeline application properties contain es.direct.push supposed to be set true for testing.
| S.No. | Property Name | Value | Description |
|---|---|---|---|
| 1. | es.direct.push | true | the transformed data will be pushed to ES index directly. |
| 2. | es.direct.push | false | the transformed data will be lying at egov-dss-ingest-enriched topic |
Step 3: Run migration Api, which migrates the data from the source index to the target index.
| S.No. | Name | Description |
|---|---|---|
Method End Point Body | POST {host}/dashboard-ingest/ingest/migrate/paymentsindex-v1/v2 {"RequestInfo":{"authToken":"2ba70924-1bba-4a9b-b55d-2e9471bf3081"}} | |
| 2. | CURL | curl -X POST https://dev.digit.org/dashboard-ingest/ingest/migrate/paymentsindex-v1/v2 -H 'cache-control: no-cache' -H 'content-type: application/json' -H 'postman-token: d83fc136-116d-265f-3b83-ea41e3d5bb57' -d '{"RequestInfo":{"authToken":"2ba70924-1bba-4a9b-b55d-2e9471bf3081"}}' |
{% hint style="info" %} Note: After migration, ensure dss-payment_v2 data has been populated and is available. {% endhint %}
In kibana, dev tools verify using below command
GET dss-payment_v2/_search