airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-2524) Airflow integration with AWS Sagemaker
Date Tue, 14 Aug 2018 23:01:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580527#comment-16580527
] 

ASF GitHub Bot commented on AIRFLOW-2524:
-----------------------------------------

troychen728 opened a new pull request #3751: [AIRFLOW-2524] Add Amazon SageMaker Tuning
URL: https://github.com/apache/incubator-airflow/pull/3751
 
 
   Make sure you have checked _all_ steps below.
   
   ### JIRA
   - [X] My PR addresses the following [Airflow JIRA](https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. 
       - https://issues.apache.org/jira/browse/AIRFLOW-2524
   
   ### Description
   - [X] Here are some details about my PR, including screenshots of any UI changes:
       - This PR allows user to start a Amazon SageMaker Hyper_Parameter_Tuning job using
the SageMakerCreateHyperParameterTuningJobOperator
       - User can also check the progress(state) of the tuning job through the SageMakerTuningSensor
   
   
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
        - tests/contrib/hooks/test_sagemaker_hook.py
        - tests/contrib/operators/test_sagemaker_create_tuning_job_operator.py
        - tests/contrib/sensors/test_sagemaker_tuning_sensor.py
         
   
   
   
   ### Commits
   - [X] My commits all reference JIRA issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   
   ### Documentation
   - [X] In case of new functionality, my PR adds documentation that describes how to use
it.
       - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   
   
   ### Code Quality
   - [X] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Airflow integration with AWS Sagemaker
> --------------------------------------
>
>                 Key: AIRFLOW-2524
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2524
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: aws, contrib
>            Reporter: Rajeev Srinivasan
>            Assignee: Yang Yu
>            Priority: Major
>              Labels: AWS
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Would it be possible to orchestrate an end to end  AWS  Sagemaker job using Airflow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message