marianobrc commented on issue #36340: URL: https://github.com/apache/beam/issues/36340#issuecomment-3361403644
> Thanks. We are looking into this. > > As a workaround, you can specify the following pipeline option when you start the job which prevents managed transforms expansion. > > `--experiments=use_pipeline_version_for_managed_transforms="beam:schematransform:org.apache.beam:iceberg_write:v1"` @chamikaramj this workaround worked great, and our pipeline runs ok now. Would it be safe for us to use this workaround in prod or do you foresee any potential issues in doing that? Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
