-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Component/s: Core DBS
-
Epic Link:
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform next
When initiating indexes in DocumentDB, components need to make sure collections have been created first.
This should already be the case for Nuxeo Repository (needs to be checked and) needs to be done for other components initiating indexes like Quartz, DirectoryService...
Here a sample failure
= Component Loading Errors: * Component service:org.nuxeo.ecm.directory.DirectoryServiceImpl notification of application started failed: Command failed with error 85: 'Implicit collection creation not supported when creating indexes' on server ***. The full response is {"code": 85, "errmsg": "Implicit collection creation not supported when creating indexes", "ok": 0.0, "errorUUID": "60aded1e-2b1e-4247-b3cb-33dfc3ecc260"} * Component service:org.nuxeo.ecm.core.repository.RepositoryServiceComponent notification of application started failed: Command failed with error 85: 'Implicit collection creation not supported when creating indexes' on server ***. The full response is {"code": 85, "errmsg": "Implicit collection creation not supported when creating indexes", "ok": 0.0, "errorUUID": "604bf7b2-360f-46f6-9d5f-1a12ebe276d0"} * Component service:org.nuxeo.ecm.core.scheduler.SchedulerService notification of application started failed: Command failed with error 85: 'Implicit collection creation not supported when creating indexes' on server ***. The full response is {"code": 85, "errmsg": "Implicit collection creation not supported when creating indexes", "ok": 0.0, "errorUUID": "d25e2534-71ff-4b1c-b195-340ce564f2a7"}