-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[batch] Add environment variable for batch id in worker #12662
Conversation
I thought I'd proposed this env variable but then we ended up going with this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above
I thought the config file was better for QoB where versioning and backwards compatibility is important and there could be substantially more configuration in the future. I don't think we mount that config file in the worker regardless for DockerJobs, but I could be wrong. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was better for QoB where versioning and backwards compatibility is important
I think we have to fulfill the same backwards compatibility with env variables, though I agree that they are more ergonomic and favorable in this case to a config file. The config file was necessary for JVMJobs because the JVM containers are long-lived, so we cannot update their environment when a new job comes in. Looks like we do write the config in DockerJobs but don't mount it, so let's add this env variable but do the following:
- Remove the use of
write_batch_config
inDockerJob
and movewrite_batch_config
fromJob
intoJVMJob
- Document where
write_batch_config
is used inJVMJob
why it's used instead of an env variable. I think I still don't understand the point of further configuration, since that's still possible with environment variables, we just can't change environment variables in JVMContainers like we can with the filesystem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome, thanks
This is needed for Siwei's recursive pipeline to work.