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

   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
   - [ ] 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-1932
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if 
applicable):
   This PR adds in a customer partitioner that is used to determine whether the 
record should exist in directory A or directory B based on the timestamp of the 
record itself. This is needed when migration from aggregate cluster ingestion 
to local cluster ingestion cutover.
   If pipeline ingesting from aggregate cluster, partitioning should include 
the consumption backup directory prefix if record is **after** the cutover 
timestamp, otherwise when **before**, use the production consumption directory 
prefix.
   If pipeline ingesting from local cluster, partitioning should include the 
consumption backup directory prefix if the record is **prior** to the cutover 
timestamp, otherwise when **after**, use the production consumption directory 
prefix.
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   Adds test for a record with timestamp before and a record with timestamp 
after the cutover time to ensure that the partitioning is correct. The 
partitioning is whether the cluster is from aggregate cluster or local cluster
   
   ### Commits
   - [ ] 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