The HTTP client used by the enrichment is injected implicitly (here, here and here).
This client uses the default http4s timeout of 45 seconds. This is very high and can introduce ever-growing latency in the pipeline.
The timeout defined in the configuration should be used. We might want to use a dedicated http4s client for the enrichment. This can be the default when we have deprecated Stream Enrich and the use of Id.
Configured timeout for API enrichment, that ends up here is never used.
The HTTP client used by the enrichment is injected implicitly (here, here and here).
This client uses the default http4s timeout of
45 seconds. This is very high and can introduce ever-growing latency in the pipeline.The timeout defined in the configuration should be used. We might want to use a dedicated http4s client for the enrichment. This can be the default when we have deprecated Stream Enrich and the use of
Id.