Will-Lo opened a new pull request, #3537:
URL: https://github.com/apache/gobblin/pull/3537

   …es do not exist or folders not matching date format
   
   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-1681] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1681
   
   
   ### Description
   - [x] Here are some details about my PR, including screenshots (if 
applicable):
   If searching through files using the timeaware dataset finder, if there are 
rogue files inside of the folders that match the datetime format (i.e. metadata 
folders by year), then it would cause the dataset finder to error out as it 
expects all folders and files to conform to the date pattern.
   
   We add a check during the listStatus step to catch these errors. Future 
improvements can be to also match folders against the date partition for that 
level before the recursive step, so that only the relevant folders will be 
searched.
   
   ### Tests
   - [x] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   
   
   ### 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