Adding Intersection API Pagination

[jacob6838]

PR Details

Description

This is a small sample PR, showing what an Intersection API custom pagination solution could look like. This implementation uses aggregation queries to complete the query and count in one operation. One concern was that these types of aggregation queries would not utilize indexes - I have confirmed that the compound index "intersectionID_-1_notificationGeneratedAt_-1" is utilized for aggregated queries to the CmConnectionOfTravel collection.
Here is a sample of the response to the /notifications/connection_of_travel?intersection_id=12109&size=1 endpoint (2 records exist):

{
    "content": [
        {
            "_id": {
                "timestamp": 1724170732,
                "date": 1724170732000
            },
            "notificationGeneratedAt": 1724170732774,
            "assessment": {
                "assessmentGeneratedAt": 1724170732774,
                "assessmentType": "ConnectionOfTravel",
                "roadRegulatorID": -1,
                "intersectionID": 12109,
                "connectionOfTravelAssessmentGroups": [
                    {
                        "egressLaneID": 5,
                        "ingressLaneID": 3,
                        "connectionID": -1,
                        "eventCount": 11
                    }
                ],
                "source": "{\"rsuId\":\"10.11.81.12\",\"intersectionId\":12109,\"region\":0}",
                "timestamp": 1724170732774
            },
            "egressLane": 5,
            "ingressLane": 3,
            "notificationText": "Connection of Travel Notification, Unknown Lane connection between ingress lane: 3 and egress lane: 5.",
            "notificationHeading": "Connection of Travel Notification",
            "roadRegulatorID": -1,
            "intersectionID": 12109,
            "notificationType": "ConnectionOfTravelNotification",
            "key": "ConnectionOfTravelNotification_12109_-1_0_0"
        }
    ],
    "pageable": {
        "pageNumber": 0,
        "pageSize": 1,
        "sort": {
            "sorted": false,
            "empty": true,
            "unsorted": true
        },
        "offset": 0,
        "paged": true,
        "unpaged": false
    },
    "last": false,
    "totalPages": 2,
    "totalElements": 2,
    "first": true,
    "size": 1,
    "number": 0,
    "sort": {
        "sorted": false,
        "empty": true,
        "unsorted": true
    },
    "numberOfElements": 1,
    "empty": false
}

How Has This Been Tested?

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• My changes require new environment variables:
  • I have updated the docker-compose, K8s YAML, and all dependent deployment configuration files.
• My changes require updates to the documentation:
  • I have updated the documentation accordingly.
• My changes require updates and/or additions to the unit tests:
  • I have modified/added tests to cover my changes.
• All existing tests pass.

[mcook42]

This is looking slick! There's one blocking chore and a few suggestions. Once you decide how you want to address the chore and suggestions, I'll be pretty quick to approve this. Nice work!

[mcook42]

great work!