You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running mlLoadSchemas or mlDeploy on a project with no schemas and no schema database will produce the following logging:
Executing command [com.marklogic.appdeployer.command.schemas.LoadSchemasCommand] with sort order [350]
Loading schemas into database myApp-schemas from: /Users/rrudin/workspace/ml-gradle/examples/local-testing-project/src/main/ml-schemas
Unable to load schemas because no schemas database exists; cause: Local message: failed to apply resource at eval: Internal Server Error. Server Message: XDMP-NOSUCHDB: No such database myApp-schemas . See the MarkLogic server error log for further detail.
Releasing connection
Finished executing command [com.marklogic.appdeployer.command.schemas.LoadSchemasCommand] in 530ms
It's not an error, but it's confusing to see that. I believe what's happening is that due to a recent change for using a new ML function for loading TDE templates, there's an attempt to connect to the schemas database, even though no schemas exist. The schemas database doesn't exist, so an error occurs.
The fix should involve ensuring that no attempt at a connection is made unless there's at least one schema to exist.
Furthermore, if there is at least one schema and the connection fails, the exception should be propagated so that the deployment fails.
The text was updated successfully, but these errors were encountered:
This is being tracked in ml-gradle but the fix will be in either ml-app-deployer or ml-javaclient-util. Once the location of the bug is determined, a ticket should be opened in the appropriate project (if we'd only known about multi-project builds in Gradle long ago...).
Running
mlLoadSchemas
ormlDeploy
on a project with no schemas and no schema database will produce the following logging:It's not an error, but it's confusing to see that. I believe what's happening is that due to a recent change for using a new ML function for loading TDE templates, there's an attempt to connect to the schemas database, even though no schemas exist. The schemas database doesn't exist, so an error occurs.
The fix should involve ensuring that no attempt at a connection is made unless there's at least one schema to exist.
Furthermore, if there is at least one schema and the connection fails, the exception should be propagated so that the deployment fails.
The text was updated successfully, but these errors were encountered: