gobblin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (GOBBLIN-881) Add job tag field that can be used to filter job statuses
Date Fri, 13 Sep 2019 23:54:00 GMT

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

ASF GitHub Bot logged work on GOBBLIN-881:

                Author: ASF GitHub Bot
            Created on: 13/Sep/19 23:53
            Start Date: 13/Sep/19 23:53
    Worklog Time Spent: 10m 
      Work Description: jack-moseley commented on pull request #2735: [GOBBLIN-881] Add job
tag field that can be used to filter job statuses
URL: https://github.com/apache/incubator-gobblin/pull/2735
   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-881
   ### Description
   - [x] Here are some details about my PR, including screenshots (if applicable):
   With multi-dataset support in gaas, it is more convenient to have an extra field that can
be used to filter when querying the job status (this would be dataset name in most cases).
   This PR allows jobs to include `job.tag` field then when querying jobStatus, specifying
tag in the query will return only job statuses with that tag.
   ### Tests
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   Updated test
   ### 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 to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

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

> Add job tag field that can be used to filter job statuses
> ---------------------------------------------------------
>                 Key: GOBBLIN-881
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-881
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: Jack Moseley
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h

This message was sent by Atlassian Jira

View raw message