[SERVER-81015] Supply unique streamProcessorID to mstreams Created: 14/Aug/23  Updated: 10/Dec/23  Resolved: 13/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Matthew Normyle Assignee: Aadesh Patel (Inactive)
Resolution: Fixed Votes: 0
Labels: init-337-m2, init-337-m3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sprint 31
Participants:

 Description   

streamProcessors need IDs to help identify them in checkpointing data. This ID should not just be the user supplied `name` of the streamProcessor. The ID can just be the ObjectID in the metadata DB, or something like `name-{random characters}`, or a UUID, etc. Choosing a unique ID allows us to distinguish when a streamProcessor of "name" has been dropped and re-created.

This ID and the tenantID needs to be supplied in the streams_startStreamProcessor request to mstreams.



 Comments   
Comment by Cloud GitHub Webhooks [ 15/Sep/23 ]

evergreen-ci-prod[bot] merged a pull request (STREAMS-528 [streams] test coverage for propagating tenant and processor ID) into the following branch:
master: fae6eeb574ceffc8368c119de90e8609cd522198

Comment by Cloud GitHub Webhooks [ 13/Sep/23 ]

evergreen-ci-prod[bot] merged a pull request (STREAMS-528 [streams] propagate tenant and processor ID to mstreams) into the following branch:
master: 97e198387b1de12646ee06ee664477cb3338747f

Generated at Thu Feb 08 06:45:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.