-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Atlas Streams
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In dev, running into a situation where after dropping a stream processor, a new one with the same name is not being created:
AtlasStreamProcessing> sp.createStreamProcessor("mk-largememtest-1", pipeline)
MongoServerError: Failed to create stream processor: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1, correlationID = 17ace57d05589d7a159978a7
AtlasStreamProcessing> sp["mk-largememtest-1"].drop()
MongoServerError: Failed to drop stream processor: stream processor doesn't exist: stream processor doesn't exist, correlationID = 17ace5806cc5f09815997948
AtlasStreamProcessing> sp.createStreamProcessor("mk-largememtest-1", pipeline)
MongoServerError: Failed to create stream processor: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1, correlationID = 17ace582dbe9439015997991
- is related to
-
-
- Closed
-