Conversation
bbrks
changed the title
manualbucketpooltest for supporting non-standard bucket testing (e.g. no _default collection)
bbrks
changed the title
manualbucketpooltest for supporting non-standard bucket testing (e.g. no _default collection)manualbucketpooltest for supporting non-standard bucket testing (e.g. no _default collection)
gregns1
left a comment
gregns1
left a comment
There was a problem hiding this comment.
TestMigrationThenDropDefaultCollectionTwoDatabases seems to fail for me for 8.0.0 version on server. When I run against 7.6.5 it passes. I can see in version 8.0.0 the indexes are stuck in building state in the UI.
I think it may be a case of collecting logs from CBS between versions and raising ticket with indexing team.
In addition, I've had TestDropDefaultCollectionDuringMigration pass and fail (it seems a bit flaky with timing issues). Given this isn’t a supported case and I think it can be hard for us to gracefully handle this situation I think it may be a candidate to drop out of this PR.
I also wonder if we should pull my test in defaultcollectiondroptest into here?
|
I know that some of the tests weren't testing things that we intended to support, but I was curious to see the behavior. I was running the tests with 8.0.1 |
- allow creating test buckets that can be dropped independently of the bucket pool. - Example of tests which do not have _default collection
Removes the standalone defaultcollectiondroptest package and merges its richer migration-then-drop scenario into TestMigrationThenDropDefaultCollection in manualbucketpooltest: assert metadata moved off _default._default, use a named-collection doc round-trip, and probe that a new opt-out database can no longer be created once _default._default is gone. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bbrks
changed the title
manualbucketpooltest for supporting non-standard bucket testing (e.g. no _default collection)
CBG-5470
_defaulttests for metadata migrationDependencies (if applicable)
Integration Tests