npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

elasticmongoose

v0.0.9

Published

Just a simple mongoose plugin for elastic search indexing

Downloads

19

Readme

ElasticMongoose

Just a simple mongoose plugin for elasticsearch indexing, based on elasticsearch.js.

Installation

cd node_modules
git clone https://github.com/Waidd/elasticmongoose.git

Or add it to your package.json

Usage

Initialization

First, you have to initialize the plugin with the connect method.

var elasticMongoose = require('elasticmongoose');

elasticMongoose.connect(function(err) {
	if (err) console.log('elasticsearch cluster down');
});

This call just initializes a client and pings the elasticsearch cluster to check if it is online. The default host will be localhost:9200. You can override options this way :

var elasticMongoose = require('elasticmongoose');

var options = {
  host : 'host.com:4242'
};

elasticMongoose.connect(function(err) {
  if (err) console.log('elasticsearch cluster down');
}, options);

Here is the list of options that you can specify :

  • index : Default index for elasticsearch, initially set to elasticmongoose.
  • findMethod : Default methods to get object from mongoose, more details in the search section.

Log

The plugin use winston to output log. The destination file is elasticmongoose.log.

Add elasticMongoose to a Schema

var mongoose = require('mongoose');
var Schema = mongoose.Schema;
var elasticMongoose = require('elasticmongoose');

var Something = new Schema({
  title : {
    type : String,
    elastic : true
  },
  description : {
    type : String,
    elastic : true
  },
  content : {
    type : String
  }
}
});

Something.plugin(elasticMongoose.mongoosePlugin(), 'something');
module.exports = mongoose.model('something', Something);

Set the fields that you want to see indexed with elastic : true. The second argument to specify to the Plugin is the options object. If you have chosen a default index in the initialization part, you just have to give the name of the type, which NEEDS to be the same as the schema name (it's necessary for the search). Otherwise you have to give the index too :

Something.plugin(elasticMongoose.mongoosePlugin(), {
  index : 'someindex',
  type : 'something'
});

Then mongoose will be automatically indexed, updated, deleted in elasticsearch while your are manipulating the mongoose object.

Nested object

The plugin will automatically detect nested object(s) :

var nestedthing = {
  city : {
    type : String,
    elastic : true //will be indexed    
  }
};

var Something = new Schema({
  title : {
    type : String,
    elastic : true
  },
  description : {
    type : String,
    elastic : true
  },
  content : {
    type : String
  },
  thing : nestedthing
}
});

Nested data will be stored at the first level of the elastic object. So the object in elastic will look like :

{
  'title' : '...',
  'description' : '...',
  'city' : '...'
}

array type

If you have to deal with a Types.Mixed, for example, to manipulate a osm address, you can use the array type :

//the mongoose schema
var SomeWhere = new Schema({
  title : {
    type : String,
    elastic : true
  },
  description : {
    type : String
  },
  address : {
    type : Types.Mixed
    elastic : 'array'
  }
});

//the mongodb object will look like
{
  title: 'somewhere',
  description: 'est sequi et cupiditate corrupti et porro nomnis...',
  address : {
    continent: 'European Union',
    country_code: 'fr',
    country: 'France',
    postcode: '...',
    state: '...',
    county: '...',
    city: '...',
    pedestrian: '...',
    house_number: '...'
  }
}

//and the elastic object
{
  title: 'somewhere',
  continent: 'European Union',
  country_code: 'fr',
  country: 'France',
  postcode: '...',
  state: '...',
  county: '...',
  city: '...',
  pedestrian: '...',
  house_number: '...'
}

function type

You can give a function instead of a type. This function will be called during the indexation of the object.

var Something = new Schema({
  title : {
    type : String,
    elastic : true
  },
  content : {
    type : String,
    elastic : function(obj, fields) {
      if (obj.indexContent)
        fields.content = obj.content.substr(0, 100);
    }
  },
  indexContent : {
    type : Boolean,
    'default' : false
  }
});

The function takes 2 parameters :

  • obj : the mongo object
  • fields : the indexed fields

geojson type

You can deal with geojson type to perform localised search.

var Somewhere = new Schema({
  title : {
    type : String,
    elastic : true
  },
  loc : {
    type : String,
    elastic : 'geojson'
  },
});

Search

var elasticMongoose = require('elasticmongoose');

elasticMongoose.search(options, query, function(err, resp){
  if(err){
    res.error(err);
  } else {
    res.json(resp);
  }
});

The options are defined by the type and the index. But once more, if you have specified a default index in the initialization part, you do not have to give it again. The type can be unique or an array of types.

options = {
  type : 'something'
}
options = {
  type : ['something', 'somewhere'],
  index : 'someindex'
}

You can specify your request by using the Elastic Search Query DSL.

Some examples :

query = {
  match : {
    title : 'Lorem ipsum dolor sit amet, consectetur adipiscing elit.',
    description: 'Etiam at mauris tristique, adipiscing enim a, malesuada nisi.'
  }
};
query = {
  multi_match : {
    query: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit.',
    fields: ['title', 'description']
  }
};
//the multi_match work with fields from different type
query = {
  filtered : {
    multi_match : {},
    filter : {
      distance : '10km',
      location : {
        lat : '45.439417',
        lon : '12.328865'
      }
    }
  }
};

ElasticMongoose will return an array of mongo objects. So it's easier to manipulate. The plugin will use the default findMethod to get the objects from mongo :

  findMethod(model, data, callback){
    model.findOne({ '_id': data._id}, function(err, instance) {
      callback(err, instance);
    });
  }

You can't overwrite it during the initialization or give a specific method for a type defining a elasticFind method to the schema.

Something.methods.elasticFind = function(model, data, callback, options){
  //options come from the fourth argument of the search method.
  model.findOne({
      '_id': data._id,
      //do some tricky conditions with the options
    })
    //populate some fields or whatever
    .populate('somefield')
    .exec(function(err, instance){
      callback(err, instance);
    });
};

Something.plugin(ElasticMongoose.mongoosePlugin(), 'event');

//then
elasticMongoose.search(options, query, function(err, resp){
  if(err){
    res.error(err);
  } else {
    res.json(resp);
  }
}, options);

If an object is still in elastic but not anymore in mongodb, the plugin will log an error with errorCallback and keep a normal behaviour. This kind of probrem can happen if the cluster is down for a while.

Truncate an index

If you need to truncate an elasticsearch index (during unit tests for example), you can use the truncate method :

  elasticMongoose.truncate(function(err){
    done(err);
  }, {
    index : 'someindex'
  });

As usual, if you specified an index during the initialization, you do not have to give any options.

Refresh an index

If you need to manually refresh an elasticsearch index (also during some unit tests), you can use the refresh method :

  elasticMongoose.refresh(function(err){
    done (err);
  }, {
    index : 'someindex'
  });

Same options management than truncate.

Todo

  • some unit tests
  • some examples
  • method to index all data in mongodb

License

The MIT License (MIT)

Copyright (c) 2014 Thomas Cholley

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.