Skip to:
Summary: using the CreatePrimaryIndexAsync throws exception when a primary index already exists, no matter what IgnoreIfExists is set to.
Repro:
Use CreatePrimaryIndexAsync to create an index.
Use CreatePrimaryIndexAsync to create an index again (with or without IgnoreIfExists set to true or false)
(see attached source code for complete example)
Expected:
If IgnoreIfExists set to true, I would expect no exception if the index already exists.
Actual:
Exception (see attached)
Notes:
Looking at the code, it appears that IgnoreIfExistsValue in CreatePrimaryQueryIndexOptions is never actually used. The ignore flag is ignored!
It's a very minor part of my Connect presentation. I'm working around it with a try/catch, NBD
Is this blocking you in any way?
I tried this against 3.0.5 release as well as the latest from github as of right now (same result)
Summary: using the CreatePrimaryIndexAsync throws exception when a primary index already exists, no matter what IgnoreIfExists is set to.
Repro:
Use CreatePrimaryIndexAsync to create an index.
Use CreatePrimaryIndexAsync to create an index again (with or without IgnoreIfExists set to true or false)
(see attached source code for complete example)
Expected:
If IgnoreIfExists set to true, I would expect no exception if the index already exists.
Actual:
Exception (see attached)
Notes:
Looking at the code, it appears that IgnoreIfExistsValue in CreatePrimaryQueryIndexOptions is never actually used. The ignore flag is ignored!