Hey hey 👋🏻 tldr: We are having an issue with an environment variable that can be passed to the GMS,

ELASTICSEARCH_INDEX_BUILDER_NUM_RETRIES

. I cannot see any change in behaviour even if I change the value of it. Can it be because this space here? This environment variable lets you to adjust how much GMS will wait for the validation of reindexing tasks it triggers on ES on Datahub version upgrades. (See flow: 1 -> 2 -> 3) We are passing this variable as we pass others on helm, from extra env vars. I can validate that it is passed to the container by describing the deployment on kubernetes. Still, we cannot observe the effect of it on the pod. I have tried to investigate the issue and see if I'm doing something silly but it seems like I'm not 😬. There is one possible cause which is an extra space in the yaml file when reading the env var to the application.yml file in here, but I couldn't reproduce the same behaviour of using the default value with this space added in my local on a different project. There is nothing online for the behaviour of spring in case of such usage of its variable substitution with additional space. Can you also take a look? I know it is a very loose question but we are kind of stuck now 😄 Should I just open a pr? Am I doing something totally wrong? Can there be an spring bean initialization issue causing

@Value

to not work(I'm so far away from spring ecosystem)

Hey @delightful-sugar-63810 thanks for reporting this. I’m not sure that that would cause an issue, but please do open a PR for it, at least for the sake of consistency (or I can if that’s easier!)

I would like open it 🔥 Let me do it. Have you also checked? I couldn't find any other possible cause on why I can't pass the value.

Thank you!

@echoing-airport-49548 I just tried with the new image pushed to the dockerhub and it now works. I'm very suprised since I couldn't reproduced the same effect with an extra space char at my local 😕 Also I know it is very far from ideal but as a documentation of the variable

ELASTICSEARCH_INDEX_BUILDER_NUM_RETRIES

, I can say that it extends the waiting period in seconds when datahub checks if the reindex is successful while doing es index migrations between datahubs version changes. This variable needs to be altered if you use your elastic search with a

refresh_interval

greater than 3 seconds(1 second is its default, see its doc in here)