rawwar opened a new issue, #59332:
URL: https://github.com/apache/airflow/issues/59332

   ### Apache Airflow Provider(s)
   
   google
   
   ### Versions of Apache Airflow Providers
   
   main
   
   ### Apache Airflow version
   
   main
   
   ### Operating System
   
   macos
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   DataprocCreateBatchOperator fails with below error when its part of a task 
group.
   
   ```
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     File 
"/usr/local/lib/python3.12/site-packages/google/api_core/grpc_helpers.py", line 
78, in error_remapped_callable
       raise exceptions.from_grpc_error(exc) from exc
   google.api_core.exceptions.InvalidArgument: 400 Not a valid value: 
"process_data". Only lowercase letters, numbers, and dashes are allowed. The 
value must start with lowercase letter or number and end with a lowercase 
letter or number.
   ```
   
   ### What you think should happen instead
   
   `__update_batch_labels` method should not use underscores. instead, it 
should use dashes - 
https://github.com/apache/airflow/blob/e0b02c9bb3aa4e0bf991d85ef1a6df4fe8e6bdcd/providers/google/src/airflow/providers/google/cloud/operators/dataproc.py#L2597
   
   ### How to reproduce
   
   Have the DataprocCreateBatchOperator task as part of a task group. I don't 
have a DAG that I can publicly share at this time. But, i'll add it soon
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to