You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/08 00:13:00 UTC

[jira] [Work logged] (GOBBLIN-678) Make flow.executionId available in the GaaS Flow config for use in job templates

     [ https://issues.apache.org/jira/browse/GOBBLIN-678?focusedWorklogId=196031&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-196031 ]

ASF GitHub Bot logged work on GOBBLIN-678:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Feb/19 00:12
            Start Date: 08/Feb/19 00:12
    Worklog Time Spent: 10m 
      Work Description: sv2000 commented on pull request #2549: GOBBLIN-678: Make flow.executionId available in the GaaS Flow config …
URL: https://github.com/apache/incubator-gobblin/pull/2549
 
 
   …for use in job templates.
   
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [x] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-678
   
   
   ### Description
   - [x] Here are some details about my PR, including screenshots (if applicable):
   Job templates would like to reference flow.executionId in the job properties (e.g. to create tmp directories that use execution id as part of the directory path). Currently, for scheduled jobs, the flow execution id is not made available in the flow config.  
   
   
   
   ### Tests
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   MultiHopFlowCompilerTest - changed job template to use flow.executionId and ensure the template is resolved during compilation.
   
   ### 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"
   
   
 
----------------------------------------------------------------
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


Issue Time Tracking
-------------------

            Worklog Id:     (was: 196031)
            Time Spent: 10m
    Remaining Estimate: 0h

> Make flow.executionId available in the GaaS Flow config for use in job templates
> --------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-678
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-678
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-service
>    Affects Versions: 0.15.0
>            Reporter: Sudarshan Vasudevan
>            Assignee: Sudarshan Vasudevan
>            Priority: Major
>             Fix For: 0.15.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Job templates would like to reference flow.executionId in the job properties (e.g. to create tmp directories that use execution id as part of the directory path). Currently, for scheduled jobs, the flow execution id is not made available in the flow config.  



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