Change Details

It's no longer running since 06/2020. This problem is 2-fold: 1.D4599: It's a configuration loading problem. It does not read its configuration even when provided. 2. D4605: The current indexer journal client implementation relies on the old origin_visit model with "status" field. As this no longer exists, the code needs to be modified to subscribe to origin_visit_status instead.

It's no longer running since 06/2020. This problem is 2-fold: 1.D4599: It's a configuration loading problem. It does not read its configuration even when provided. 2. D4605: The current indexer journal client implementation relies on the old origin_visit model with "status" field. As this no longer exists, the code needs to be modified to subscribe to origin_visit_status instead.

It's no longer running since 06/2020. This problem is 2-fold: 1.D4599: It's a configuration loading problem. It does not read its its configuration even when provided. 2. D4605: The current indexer journal client implementation relies on the old old origin_visit model with "status" field. As this no longer exists, the code needs to be modified to subscribe to origin_visit_status instead.