It's all about the answers!

Ask a question

Multiple UUID's for a stream

Rakesh Dama (1510) | asked Jan 06 '17, 2:56 p.m.

I have a stream having 3 UUID's. when I try to use command line options it's showing like

Ambiguous selector "Main_str" matched multiple items:

Possible matches:

  (1089) "Main_str"

  (1090) "Main_str"

  (1091) "Main_str"

Problem running 'workspace add-flowtargets':

Ambiguous workspace/stream "Main_str"

But, when I list the streams it's showing only one stream with UUID 1090. How does it possible?

when UUID gets generated?

is it possible for one stream having multiple UUID's ?

How multiple UUID's for one stream gets generated? and, bestway to get rid of duplicate/unnecessary UUID's and how to prevent ?


R Dama

Accepted answer

permanent link
Lily Wang (4.9k714) | answered Jan 08 '17, 8:04 p.m.

The IDs you saw are not UUID but stream's aliases. It's NOT possible for a stream to have multiple UUIDs or multiple aliases.

I don't know which command you ran to get the issue. But "Ambiguous selector" means you have multiple streams which have the same name in the RTC repository. You should avoid to create stream with the same name by using some naming convention.

Ralph Schoon selected this answer as the correct answer

Rakesh Dama commented Feb 09 '17, 7:45 p.m. | edited Sep 04 '17, 2:51 p.m.

The rootcause is we have workspaces created exactly with same name as stream.

So the commands I use will look for the stream/workspace name to load and caused ambiguous.

Your answer

Register or to post your answer.