mongoTrek is a a Java library inspired by Liquibase for managing collection and document migrations within your application's database.

This library is a "roll-forward" migration tool, meaning that to rollback changes, new migrations are required to undertake this task.

mongoTrek is a fork from the Java Mongo Migrations project. As such, projects that have previously managed migrations using this project can upgrade to mongoTrek and it will understand the previous migrations schema version collection documents.

<dependency>
    <groupId>net.ozwolf</groupId>
    <artifactId>mongo-trek</artifactId>
    <version>${current.version}</version>
</dependency>

compile 'net.ozwolf:mongo-trek:${current.version}'

As part of your own project, you will need to include the following dependencies:

Build Version: 3.2.0

<dependency>
    <groupId>org.mongodb</groupId>
    <artifactId>mongo-java-driver</artifactId>
    <version>[3.2.0,)</version>
</dependency>

mongoTrek uses the MongoDB database commands framework to execute commands.

Refer to the MongoDB Database Commands documentation.

The migrations file for mongoTrek is a YAML or JSON file that is either a resource in your classpath or a file on your file system. The library will first scan the classpath before the file system.

Each migration entry consists of:

• version [ REQUIRED ] - A unique version identifier. Migrations will be played in schemantic version order, regardless of their order in the migrations file (eg. version 2.0.0 will always be played ahead of 2.0.0.1)
• description [ REQUIRED ] - A short description of the migrations purpose
• author [ OPTIONAL ] - The author of the migration. If not supplied, the author will be recorded as trekBot
• command [ REQUIRED ] - The database command to run. Because mongoTrek uses YAML, this can be in the form of a direct JSON or YAML structure, as long as it meets the MongoDB Database Command requirements.

migrations:
    - version: 1.0.0
      description: populate people base data
      author: John Trek
      command: {
        insert: "people",
        documents: [
            { name: "Homer Simpson", age: 37 },
            { name: "Marge Simpson", age: 36 }
        ]
      }
    - version: 1.0.1
      description: populate town base data
      command: {
        insert: "town",
        documents: [
            { name: "Springfield", country: "USA" },
            { name: "Shelbyville", country: "USA" }
        ]
      }

For commands such as the MapReduce Command, functions should be enclosed as strings. For example:

migrations:
    - version: 1.0.0
      description: run a map-reduce
      command: {
        mapReduce: "towns",
        map: "function() { emit(this.country, 1); }",
        reduce: "function(country, towns) { return Array.sum(towns); }",
        out: "town_counts"
       }

To run your migrations, provide either a MongoDB Connection String URI or a MongoDatabase instance on initialization.

You can then either migrate your database (MongoTrek.migrate(<file>)) or request a status update (MongoTrek.status(<file>)). Both methods will return a MongoTrekState, allowing you to query applied, pending and current migration versions.

public class MyApplication {
    private final static Logger LOGGER = LoggerFactory.getLogger(MyApplication.class);
    
    public void start() {
        try {
            MongoTrek trek = new MongoTrek("mongodb/trek.yml", "mongodb://localhost:27017/my_app_schema");
                    
            trek.setSchemaVersionCollection("_my_custom_schema_version");
            
            MongoTrekState state = trek.migrate();
            
            LOGGER.info("Successfully migrated schema to version: " + state.getCurrentVersion());
        } catch (MongoTrekFailureException e) {
            LOGGER.error("Failed to migrate database", e);
            
            System.exit(-1);
        }
    }
}

mongoTrek uses the LOGBack project log outputs.

The logger in question is the MongoTrek class logger (ie. Logger migrationsLogger = LoggerFactory.getLogger(MongoTrek.class);)

You can configure the output of migrations logger using this class.

Messages are logged via the following levels:

• INFO - All migration information (ie. configuration, versions, migration information)
• ERROR - If an error occurs (ie. invalid migration command definition or general connection/execution errors)

• Fongo
• LOGBack