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
BIG_QUERY_WITH_DIRECT_RUNNER_BEAM_PIPELINE_ARGS= [
'--project='+GOOGLE_CLOUD_PROJECT,
'--temp_location='+os.path.join('gs://', GCS_BUCKET_NAME, 'tmp'),
'--runner=DataflowRunner',
'--region=us-central1',
'--experiments=upload_graph', # must be enabled, otherwise fails with 413'--dataflow_service_options=enable_prime',
'--autoscaling_algorithm=THROUGHPUT_BASED',
]
Not sure if related but with the above preprocessing_fn, my transform first failed with the error:
RuntimeError: The order of analyzers in your `preprocessing_fn` appears to be non-deterministic. This can be fixed either by changing your `preprocessing_fn` such that tf.Transform analyzers are encountered in a deterministic order or by passing a unique name to each analyzer API call.
I then added names to the tft.scale_to_0_1 analyzers:
After which my transform just silently failed without logs (see first screenshot). I check the worker logs but there's nothing substantial, only warnings (see second screenshot).
It's worth noting that I have the enable_prime flag.
The text was updated successfully, but these errors were encountered:
Could you please take a look at this issue and see if it helps in resolving your issue? Also you can refer to this doc which discusses about the error you mentioned. Thanks!
System information
KubeflowV2DagRunner
)Here's my
preprocessing_fn
(redacted for clarity):Here's the
beam_pipeline_args
:Not sure if related but with the above
preprocessing_fn
, my transform first failed with the error:I then added names to the
tft.scale_to_0_1
analyzers:After which my transform just silently failed without logs (see first screenshot). I check the worker logs but there's nothing substantial, only warnings (see second screenshot).
It's worth noting that I have the
enable_prime
flag.The text was updated successfully, but these errors were encountered: