Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
4.0.0
-
None
-
Untriaged
-
Unknown
Description
From forums post https://forums.couchbase.com/t/interesting-gsi-index-behavior/7598 …
Let's say I create a new bucket from scratch. I then go into cbq and issue a big pile of CREATE INDEX (....) WITH GSI
{"defer_build":true}statements. (With the intention of later issuing a BUILD INDEX statement).
Further suppose I never issue that BUILD INDEX statement. (Usually because I've screwed my code up). So what you end up with is a pile of indexes labeled "Created" at 0% build. Which makes sense, because you haven't started building them yet. Fine.
The strange part is, if I at this point delete the bucket, and re-create it, I can't shake those indexes, even if the original CREATE INDEX statements were on that bucket. Indeed re-trying the index creation loop fails, because they already exist!
Attachments
Issue Links
- duplicates
-
MB-16999 GSI index survive a bucket deletion in deferred build edge case
- Resolved