Skip to content

issues/150: Added support for NRT filtering by granule id, minor fixes#178

Open
jackiryan wants to merge 2 commits into
developfrom
issues/150
Open

issues/150: Added support for NRT filtering by granule id, minor fixes#178
jackiryan wants to merge 2 commits into
developfrom
issues/150

Conversation

@jackiryan
Copy link
Copy Markdown
Contributor

Github Issue: #150 , as well as #83 and a minor unticketed change

Description

As part of the work required to support MODIS L3 SST Daily collections, we need to be able to configure a regex to decide whether a granule gets delivered to GIBS in an NRT or Standard bucket. For these collections, NRT granules are mixed in with standard and are differentiated by filename where the former have a ".NRT" designation at the end.

Example: https://search.earthdata.nasa.gov/search/granules?p=C2036880650-POCLOUD&pg[0][v]=f&pg[0][gsk]=-start_date&q=MODIS%20AQUA%20L3%20SST

Overview of work done

  • Added a new nrtFilenameRegex keyword to the dataset config allowing the provider to specify a regex to use for filtering NRT granules into a separate bucket for GIBS delivery
  • Updated create_dataset_config.py script and CONFIGURATION.md documentation to allow for datasets to be configured with new keyword
  • Added documentation in readme for the new keyword
  • Removed redundant md5 checksum calculation in "process_harmony_results" in the handle_big_result lambda. This is a minor performance optimization noted during NISAR testing that was never specifically ticketed.
  • Replace ":" in timestamps with "_" in CNM filenames, A : being used when creating filename creates issues on Mac and Linux #83 . This is an incredibly minor change so I just rolled it into this update.

Overview of verification done

Unit tests have been updated to reflect the updated behavior in the handle_big_result lambda and are all passing.

SIT testing TBD. I specifically need to test configuring a daily MODIS collection and using the filename regex.

Overview of integration done

Integration testing is N/A and requires a UAT deployment and support from GITC Ingest team to see if our NRT bucket key will be handled appropriately. This can be tested with the rest of the updates in the main 0.8.0 release.

PR checklist:

  • Linted
  • Updated unit tests
  • Updated changelog
  • Integration testing (N/A, to be done later when testing release/0.8.0)

See Pull Request Review Checklist for pointers on reviewing this pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: needs:triage

Development

Successfully merging this pull request may close these issues.

2 participants