Skip to content
This repository has been archived by the owner on Aug 31, 2022. It is now read-only.

Java properties are not passed to forked task #101

Open
labianchin opened this issue Jul 5, 2018 · 4 comments
Open

Java properties are not passed to forked task #101

labianchin opened this issue Jul 5, 2018 · 4 comments

Comments

@labianchin
Copy link
Contributor

labianchin commented Jul 5, 2018

With the introduction of ForkingExecutor, I started noticing some errors on BQ flo tasks.

It seems to be related to the fact that I am running the flo process with -DGOOGLE_CLOUD_PROJECT=my-gcp-project and that system property definition is not passed to the the forked task subprocess.

To fix that would require some changes on ForkingExecutor, I guess something related to this.

@danielnorberg
Copy link
Contributor

I remember writing the code to propagate properties but maybe it got lost in a rebase. Will fix.

@danielnorberg
Copy link
Contributor

Found it: #105

@labianchin
Copy link
Contributor Author

Great!

Still, there can be the case of System properties being configured outside of the command line e.g. with System.getProperties().setProperty(). Maybe we don't have to fix for that, but at least acknowledge the limitation in the documentation. WDYT?

@danielnorberg
Copy link
Contributor

Maybe system properties and env vars is something that should be configurable per task? Or maybe it’s something that could/should be doable using a task context.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants