Project with multiple content databases each with it's own triggers database

[peetkes]

How would one go about the following scenario?
I have two main databases and I need a set of triggers working on database 1 and another set of triggers working on database 2
The triggers for database2 should not run on database 1.
Configurationwise I would create two main databases each with its own triggers database. But how can I configure the triggers in such a way that each triggers database has it's own set of trigger configurations?

[rjrudin]

This is possible with some build.gradle surgery. The basic approach is (haven't tested this, but I think this will work):

You'll need to make an additional task that is run after mlDeploy - e.g. via "mlPostDeploy.dependsOn myCustomTriggersTask" .

That task will do a very limited version of what mlDeploy does, which is - instantiate a SimpleAppDeployer (from ml-app-deployer), and only run DeployTriggersCommand.

The key is that the AppConfig object that you pass to SimpleAppDeployer.deploy will need two things modified - "setTriggersDatabaseName" and "setConfigDir". That allows you to target a different triggers database and a different configuration directory.

That assumes that you structure your project files something like this:

• src/main/ml-config = where all the regular stuff goes
• src/main/ml-secondary-triggers = name this whatever you'd like; this would be a separate configuration directory that only has the triggers in it for the second triggers database

Let me know if you need some help with this - if I free up some time, I'll throw together a little prototype of it, as it should just be a handful of lines of code, just need to know what those are.

Also, let me know how you'd like to see this supported via properties instead of build.gradle surgery. Ideally, we'd want to support N triggers databases and N triggers directories. I think one way would be like this:

• ./databases/my-database/triggers/*.xml
• ./databases/my-other-database/triggers/*.xml

And then ml-gradle would be smart enough to say - I'll look up the triggers database associated with each database (whose name matches the directory) and load the triggers into that triggers database.

[rjrudin]

I'm pretty certain that the "triggers directory per database directory" is the way to go, I'm going to open a ticket in ml-app-deployer for it.

[rjrudin]

Try this, I think it'll do the job - customize the values as needed:

task deployMyOtherTriggers {
  doLast {
    def deployer = new com.marklogic.appdeployer.impl.SimpleAppDeployer(mlManageClient, mlAdminManager, new com.marklogic.appdeployer.command.triggers.DeployTriggersCommand())
    mlAppConfig.setTriggersDatabaseName("other-triggers-database")
    mlAppConfig.setConfigDir(new com.marklogic.appdeployer.ConfigDir(new File("src/main/other-triggers")))
    deployer.deploy(mlAppConfig)
  }
}

mlPostDeploy.dependsOn deployMyOtherTriggers

[peetkes]

I like the config way over the custom gradle task. Thanks for your help, will give the custom task a spin

[rjrudin]

@peetkes 3.6.2 of ml-gradle has support for deploying triggers to different databases now