homatthew opened a new pull request, #3507:
URL: https://github.com/apache/gobblin/pull/3507

   Revert "Fix bug when shrinking the container in Yarn service (#3504)"
   This reverts commit dd6d910a7e7a90d15258c6c77ebe626ae6d573f9.
   
   Revert "[GOBBLIN-1620]Make yarn container allocation group by helix tag 
(#3487)"
   This reverts commit 3e877951c284ccd68be3634522f9fc2c3d39f81a.
   
   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-1646] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1646
   
   
   ### Description
   - [X] Here are some details about my PR, including screenshots (if 
applicable):
   
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   Tested on parallel test pipeline for regressions. Data is landing for 
`/data/tracking/streaming_parallel_test/PageViewEvent/hourly/2022/05/12/10`
   
   ### 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to