This request resubmits messages with a unique_id within the given IDs. Unique_id consists of broker_id and message_id of the stored message in the data lake: Unique_id = {broker_id}_{message_id}. To resubmit messages with some exact ID, a POST request to http://<rsb-host>:8081/resubmit/<mongo-collection>?topic=<resubmit-topic> must be sent with the request body containing an array of IDs of the messages to be resubmitted.

{
    "ids": ["msg-topic_2523966771678879", "msg-topic_2523966771678312"]
}

This can also be done using curl:

curl -XPOST -H "Content-type: application/json" -d '{
    "ids": ["msg-topic_2523966771678879", "msg-topic_2523966771678312"]
}' 'http://<rsb-ip-address>:8081/resubmit/<mongo-collection>?topic=<resubmit-topic>'

An example of a successful response is:

{
    "status": 200,
    "msg": "resubmission succesful",
    "summary": {
        "indexed_count": 2,
        "fetched_count": 2,
        "deserialized_count": 2,
        "published_count": 2
    }
}

If the IDs given in the body don’t have corresponding messages in the MongoDB, Status 200 OK without errors is returned, but the counters show that the messages were not successfully found in the database and were not published.

Range request is used to resubmit all messages from a given broker_id and in the given time interval/range.

To resubmit all messages from a given topic and in the given time interval, a POST request to http://<rsb-host>:8081/range/<mongo-collection>?topic=<resubmit-topic> must be sent with the request body containing the broker_id which value is topicID from which the messages were initially ingested.

Optionally, two other body request parameters can be defined:

• lb is the lower bound of the time interval (the one further back in time)
• ub is the upper bound of the time interval (the more recent time)

If an interval bound parameter is omitted, a default value is used instead. For the lower bound, the default value is 0001/01/01 00:00:00.000000000 UTC, while for the upper bound it is the moment the request had been made.

An example /range request:

{
    "broker_id": "per-test-topic",
    "lb": "0001-01-01T00:00:00Z",
    "ub": "2021-09-27T14:15:05Z"
}

This can also be done using curl:

curl -XPOST -H "Content-type: application/json" -d '{
    "broker_id": "per-test-topic",
    "lb": "0001-01-01T00:00:00Z",
    "ub": "2021-09-27T14:15:05Z"
}' 'http://<rsb-host>:8081/range/<mongo-collection>?topic=<resubmit-topic>'

The query request is used to resubmit all messages satisfying the custom query filter, i.e. containing exact Persistor-generated metadata values given in the request body. To use this method, a POST request to http://<rsb-host>:8081/query/<mongo-collection>?topic=<resubmit-topic> must be sent with the request body containing the filters used.

The query filters are defined as an array of JSON objects, where each filter is represented by one object and it filters data that satisfies all of its fields. Then, all the filters are combined using the OR logical operation, meaning any data that satisfies at least one full filter is resubmitted.

JSON fields for a filter should be metadata field names, while their value should either be the exact value to be queried for or a JSON object containing more advanced information for querying.

Special keywords that can be used in JSONs:

Example of the request body containing filtering information:

{
    "filters" : [
        {
            "additional_metadata.a" : "x",
            "location_position" : {
                "$gte": 88, "$lt": 91
            },
            "publish_time": {
                "$gte": "2023-02-05 19:20:55.342"
            }
        },
        {
            "additional_metadata.b" : "y"
        }
    ]
}

which, by using curl, can be sent as:

curl -XPOST -H "Content-type: application/json" -d '{
    "filters" : [
        {
            "additional_metadata.a" : "x",
            "location_position" : {
                "$gte": 88, "$lt": 91
            },
            "publish_time": {
                "$gte": "2023-02-05 19:20:55.342"
            }
        },
        {
            "additional_metadata.b" : "y"
        }
    ]
}' 'http://<rsb-host>:8081/query/<mongo-collection>?topic=<resubmit-topic>'

Let’s say there are 80 messages with "additional_metadata.a" : "x" (meaning the message’s additional metadata has to have the field “a”, and its value has to be “x”), but only 10 of them have “location_position” in [88, 91), and only 5 of those have “publish_time” after “2023-02-05 19:20:55.342” - those 5 messages would be the result for the first query filter.

In addition, if there are 100 messages with "additional_metadata.b" : "y", all of those messages will also be resubmitted. If there is an intersection between those two filter results, those messages are resubmitted only once.

It is important to note that if timestamps must be given in the format used in the example - yyyy-MM-dd HH:mm:ss.

Furthermore, additional metadata is best defined using single fields and values for those fields, but it can also be defined as a JSON, IE.

{
    "additional_metadata" : {
        "b": "y",
        "a": "x"
    }
}

but in that case, all fields must have correct values and their order must be the same as in the query.

If a query filter key is not a valid Persistor metadata field, an error containing the invalid keys will be returned.