evgenyslab opened a new pull request, #37552:
URL: https://github.com/apache/airflow/pull/37552

   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   
   Update logic in `Amazon/aws` providers for `batch_client` `hook`'s 
`parse_job_description` function. This function is ONLY called within the 
`get_job_description` function that allows for retries; however, there is only 
handling of `botocore.exceptions.ClientError` error in this function.
   
   This means, that if AWS simply fails to provide the job description - if 
there is a delay in AWS to register job information, this function will 
immediate fail instead of trying. This may happen under certain conditions, 
especially when using the `batch` operators for submitting jobs which 
immediately use returned `job_id` to query for the job information - but again, 
if AWS fails to register the job description in time - this will cause an 
unnecessary failure in Airflow side of things.
   
   The proposed change allows `parse_job_description` to return `None` instead 
of raising if zero jobs are returned by AWS. Similarly, if more than one 
matching job is returned, the function will provide the description of the 
first job.
   


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to