Legacy/Re-Indexing the Water & Sewerage Service

Overview

We are using re-indexing to get all the data to the respective indexer. We have 2 steps for this. The first is to run the connector from the playground. This is followed by a legacy indexer service call from the indexer service, which internally calls the respective plain search service to get the data and send it to the respective indexer.

Pre-requisites

  • Access to kubectl of the environment targetted

  • Postman scripts

  • Plain search APIs in the respective services

Configuration Steps

We have two services for water and sewerage

  • water-services

  • sewerage-services

Water-services Reindexing Steps

  • Connect to playground pod.

  • Delete the Kafka connector if already exists with the Kafka connection, using the below command through playground pod.

curl --location --request DELETE 'http://kafka-connect.kafka-cluster:8083/connectors/water-services-enriched-es-sink'
  • Run below Kafka connector curl from playground pod:

  • port forward to egov-indexer pod and run below curl throw postman.

  • Delete the Kafka connection after all the data has been re-indexed by following the below command through the playground pod.

  • Alias water-services-enriched as water-services through the Kibana server.

Sewerage-services Reindexing Steps

  • Connect to playground pod.

  • Delete the Kafka connector if already exists with the Kafka connection, using the below command through playground pod.

  • Run below Kafka connector curl from playground pod:

  • port forward to egov-indexer pod and run below curl throw postman.

  • Delete the Kafka connection after all the data has been re-indexed by following the below command through the playground pod.

  • Alias water-services-enriched as water-services through the Kibana server.

Last updated

Was this helpful?