-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Collection Management
-
Needed
-
Summary
b042e47 introduced spec tests where clusteredIndex is specified as an option for the create command helper (e.g. Database.createCollection). These tests do not actually assert that the option is passed to the server. In particular, the "createCollection with clusteredIndex" test only asserts that the newly created collection exists after the createCollection operation is executed.
Thankfully, the "listCollections includes clusteredIndex" and "listIndexes returns the index" should be suitable guarantee driver correctness, since those tests will fail if clusteredIndex is not correctly passed to create.
Motivation
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- is related to
-
DRIVERS-1853 Clustered Indexes for all Collections
- Closed
- split to
-
CXX-2515 Add commandStartedEvent assertions to clustered index spec tests
- Backlog
-
CDRIVER-4392 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
CSHARP-4177 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
GODRIVER-2424 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
MOTOR-965 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
NODE-4255 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
PHPLIB-874 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
PYTHON-3274 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
RUBY-3002 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
RUST-1329 Add commandStartedEvent assertions to clustered index spec tests
- Closed
-
JAVA-4618 Add commandStartedEvent assertions to clustered index spec tests
- Closed