Sanitation
PlatformDomainsAcademyDesign SystemFeedback
v1.3.1
v1.3.1
  • Introducing DIGIT Sanitation
    • Roadmap
    • Who can use DIGIT Sanitation?
      • Field Research
  • Platform
    • Features
    • Release Notes
      • Test Cases
      • Service Build Update
        • Release Builds for DIGIT 2.8
      • MDMS Configuration Updates
      • Test Cases for Urban-Rural Convergence
      • Localisation
      • Impel Release Notes
    • Architecture
    • Installation
    • Setup
      • On AWS
    • Operations Guide
    • Development Guide
      • Backend Developer Guide
      • UI Developer Guide
    • Source Code
  • Product
    • Faecal Sludge Management (FSM)
      • Features
      • Sanitation Actors & Interactions
      • User Interface Design
      • FSM Core Service Configuration
        • FSM Implementation Configuration
        • FSM Calculator
        • FSM Vendor Registry
          • Workflow Service
            • Configuring Workflows For New Product/Entity
            • Setting Up Workflows
            • Workflow 2.0 Configuration
          • User Service
            • User Data Encryption Promotion
            • Encryption Client Library
          • API Contract
        • FSM Vehicle Registry
        • Legacy/Re-Indexing the FSM Data
        • FSM UI Docs
          • FSM Citizen UI
          • FSM Employee UI
          • FSM DSO UI
          • FSM FSTPO UI
        • FSM-DSS Technical Documentation
      • FSM User Manual
        • FSM Citizen User Manual
        • FSM Employee User Manual
          • Manage Vendor, Driver and Vehicle Details
        • DSO User Manual
        • Septage Treatment Plant Operator User Manual
      • Test Cases
      • FSM UI/UX Audit
      • FSM Functional Specification
      • FSM Technical Specification
        • Vehicle Technical Specification
        • Vendor Technical Specification
        • Calculator Technical Specification
      • FSM Release Notes
      • Training
  • Programme
    • Functional Customisation
      • Urban-Rural Convergence
    • Technical Customisation
    • Technical Specification: Urban-Rural Convergence
    • Standard Operating Procedure (SOP)
    • Program Rollout Plan
    • Adoption Metrics
    • Implementation Plan
    • Implementation Guide
      • General FSM Implementation Activities
    • Implementation Checklist
  • COMMUNITY
    • Contribute
    • Issues
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Overview
  • Pre-Requisites
  • Steps to legacy-index FSM
  • Steps to legacy index VehicleTrip

Was this helpful?

Export as PDF
  1. Product
  2. Faecal Sludge Management (FSM)
  3. FSM Core Service Configuration

Legacy/Re-Indexing the FSM Data

Last updated 1 year ago

Was this helpful?

Overview

In this document, we will learn how to legacy index/re-index the fsm index.

Pre-Requisites

  • Kubectl access to the required environment in which you want to run the re-indexing

  • playground pod access

  • Legacy index mapping/configuration done in the respective indexer-config ( in this case for FSM, legacy index configuration for fsm is done , Similarly for VehicleTrip also exists )

Postman Collection

Postman collection to re-index the data for FSM, VehicleTrip, Vehicle, Vendor Services can be downloaded

Steps to legacy-index FSM

  1. After importing the postman collection downloaded from above section, you can find two request

    1. fsm-legacy : This request helps to get the data from fsm/plainsearch api and push data to fsm-enriched topic by indexer service

    2. fsm-legacy-kafkaconnector : This is the request to create a connector which can listen to the fsm-enriched topic and push data to the elastic search with the new index fsm-enriched

  2. Run the fsm-legacy-kafkaconnector request in the playground pod, which would create a connector which would intern start listening to the topic fsm-enriched-sink

  3. Run the fsm-legacy request in the playground pod, which would call indexer service to intiate the process of fetching the data from plainsearch and push the data prepared according to the legacy-index mapping and push the data to the fsm-enriched-sink topic

  4. Whole process would take some time, mean while you can searc for the data in fsm-enriched index in the elastic search

  5. we can go through the logs of the indexer pod, which would help to understand the job is done

  6. Once the job is done, delete the kafka connector running the below curl in the playground curl --location --request DELETE 'http://kafka-connect.kafka-cluster:8083/connectors/fsm-enriched-es-sink'

  7. Once reindexing is completed, please verfiy the count in fsm index and fsm-enriched index, then delete the fsm index and create alias for fsm-enriched index as fsm.Please use below command for alias creating.

POST /_aliases
{  "actions":
[  
  {      "add":
 {        "index": "fsm-enriched",    
   "alias": "fsm"    
  }    
}
 ]
}

Steps to legacy index VehicleTrip

  1. After importing the postman collection downloaded from above section, you can find two request

    1. vehicleTrip-legacy : This request helps to get the data from vehicletrip/plainsearch api and push data to vehicletrip-enriched topic by indexer service

    2. vehicle-trip-legacy-kafkaconnector : This is the request to create a connector which can listen to the vehicletrip-enriched topic and push data to the elastic search with the new index vehicletrip-enriched

  2. Run the vehicletrip-legacy-kafkaconnector request in the playground pod, which would create a connector which would intern start listening to the topic vehicletrip-enriched-sink

  3. Run the vehicletrip-legacy request in the playground pod, which would call indexer service to intiate the process of fetching the data from plainsearch and push the data prepared according to the legacy-index mapping and push the data to the vehicletrip-enriched-sink topic

  4. Whole process would take some time, mean while you can searc for the data in vehicletrip-enriched index in the elastic search

  5. we can go through the logs of the indexer pod, which would help to understand the job is done

  6. Once the job is done, delete the kafka connector running the below curl in the playground curl --location --request DELETE 'http://kafka-connect.kafka-cluster:8083/connectors/vehicletrip-enriched-es-sink'

  7. Once reindexing is completed, please verfiy the count in vehicletrip index and vehicletrip-enriched index, then delete the vehicletrip index and create alias for vehicletrip-enriched index as vehicletrip.Please use below command for alias creating.

POST /_aliases
{  "actions":
[  
  {      "add":
 {        "index": "vehicletrip-enriched",    
   "alias": "vehicletrip"    
  }    
}
 ]
}
here
here