Context environment get the wrong value in subjob - Logging process

[Anonymous]

Hello,

I'm facing an issue when trying to pass a different environment context to subjobs by command line. By default I'm passing the DEV environment, but when I run the job by command line passing a different context, (using --context=PRD for example), in the subjobs the environment in the tStatsCatcher "context" variable still get the default, which is DEV. I think that is because in the subjob call, I need to inform which context the subjob should run, like image below.

Exist a way that I can replicate the context used in command line by all subjobs?

Thank you!

[billimmer]

In my experience, if you check the "Transmit whole context", then the subjob will get the values from the main job.  But...  in the logging I still see the wrong context shown.  But it does work and the values are passed as long as the variable names are the same between main and sub.

You should be able to create a small test job to prove this.

[Anonymous]

Thank you for your reply @lli,

Yeah, the subjob work perfectly when I use "Transmit whole context". It is actually working normally with this configuration, but in the log it shows the default context, which in subjobs is always the same DEV. I think I will create a context variable to pass the context information in the main job and use this variable to log the context in all child jobs, but this will be a hard thing to do since I will need to create one more context variable in all subjobs...

If Talend have some better solution to resolve this, please let me know.

Luiz Ramos

[MBeaujoin1649763554]

Does anyone know how to have accurate logs ?

I came accross the same problem recently, got confused a bit. But context appears to work fine in the end, even when the logs says otherwise.

But having accurate logs is still an important bit of my work.

Does anyone know how to make sure the logs remain accurate ?