Description
If you create an index on a bucket, I created an index on an empty bucket
create index idx2 on default(fake)
When I run an explain on this I get this output:
explain create index idx2 on default(fake)
[
{
"code": 4300,
"msg": "The index idx2 already exists.",
"query_from_user": "explain create index idx2 on default(fake)"
}
]
But the explain should not retry the index creation isn't that correct? The logs are attatched, the bucket is empty, no indexes in the beginning. I found this bug due to a test that loads a full bucket, creates an index on that bucket, then runs an explain on that index creation. You can run
./testrunner -i VMs.ini -p doc-per-day=6,gsi_type=memory_optimized,nodes_init=2,primary_indx_type=GSI,use_rest=False -t tuqquery.tuq_index.QueriesViewsTests.test_intersect_scan,index_field=join_mo;join_day,test_to_run=test_comparition_equal_not_equal
to reproduce exactly, however the above empty bucket scenario seems to fail as well.
Attachments
Issue Links
- relates to
-
MB-19357 Difference in behaviour between prepared and direct create [primary] index statements
- Closed