You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.The text was updated successfully, but these errors were encountered: