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 🙏

© 2024 – Pkg Stats / Ryan Hefner

esmongo

v1.0.2

Published

Mongoose + Elasticsearch with Heroku and Bonsai Support

Downloads

6

Readme

#esmongo

##The Power of Elasticsearch for Mongoose.

esmongo is a mongoose plugin that integrates your data with Elasticsearch, to give you the full power of highly available, distributed search across your data.

esmongo is a fork of eesmongo. It is compatible with Elastic Search 1.x and Heroku Bonsai add-on. It also provides more flexible where clause options.

If you have homebrew, you can install and run Elasticsearch with this one-liner:

brew install elasticsearch && elasticsearch

Migration from 0.1.x

Pagination

version 0.1.x

// Paginate through the data
Cat.search({ query: '*', page: 2, pageSize: 25 }, function (err, results) {
  // ...
})

new versions

// Paginate through the data
Cat.search({ query: '*', from: 25, size: 25 }, function (err, results) {
  // ...
})

Note: consistent with pagination for Elastic Search

#Install

npm install esmongo

#Usage

var mongoose = require('mongoose'),
    esmongo = require('esmongo'),
    Schema = mongoose.Schema

var CatSchema = new Schema({
    name: String
})

// add the esmongo plugin to your collection
CatSchema.plugin(esmongo)

var Cat = mongoose.model('Cat', CatSchema)

Now setup the search index with your data:

Cat.sync(function (err, numSynced) {
  // all cats are now searchable in elasticsearch
  console.log('number of cats synced:', numSynced)
})

At this point your Cat schema has all the power of Elasticsearch. Here's how you can search on the model:

Cat.search({ query: 'simba' }, function (err, results) {
 	console.log('search results', results)
})

// Perform a fuzzy search
Cat.search({ query: 'Sphinxx', fuzziness: 0.5 }, function (err, results) {
	// ...
})

// Search in specific fields
Cat.search({ query: 'Siameez', fuzziness: 0.5, fields: [ 'breed'] }, function (err, results) {
    // ...
})

// Paginate through the data
Cat.search({ query: '*', from: 0, size: 25 }, function (err, results) {
 	// ...
})

// Use `where` clauses to filter the data
Cat.search({ query: 'john', where: { age: 25, breed: 'siamese' } }, function (err, results) {
	// ...
})

// The `where` clauses support `and` and `or`
Cat.search({ query: 'john', where: { and: [{or: [{age: 25}, {breed: 'siamese'}]}, {age:30}] }, function (err, results) {
  // ...
})

// The `where` clause has full support for raw elastic search filters via `$raw`
// You can also mix the high-level lmonogo filter and the low-level elastic search filter together
Cat.search({ query: 'john', where: { and: [{age:30}, {'$raw': {not: {ids: ["53de7747bb8b38f39b7efe28"]}}}] }, function (err, results) {
  // ...
})

To use raw elastic search filter, please refer to Elastic Search Filter Guide

After the initial .sync(), any Cat models you create/edit/delete with mongoose will be up-to-date in Elasticsearch. Also, esmongo reindexes with zero downtime. This means that your data will always be available in Elasticsearch even if you're in the middle of reindexing.

#API

##Model.sync(callback)

Re-indexes your collection's data in Elasticsearch. After the first .sync() call, Elasticsearch will be all setup with your collection's data. You can re-index your data anytime using this function. Re-indexing is done with zero downtime, so you can keep making search queries even while .sync() is running, and your existing data will be searchable.

Example:

Cat.sync(function (err, numSynced) {
	// all existing data in the `cats` collection is searchable now
    console.log('number of docs synced:', numSynced)
})

##Model.search(searchOptions, callback)

Perform a search query on your model. Any values you provide will override the default search options. The default options are:

{
    query: '*',
    fields: [ '_all' ],	// searches all fields by default
    fuzziness: 0.0,		// exact match by default
    size: 25,
    from: 0
}

##Model.plugin(esmongo[, options])

Gives your collection .search() and .sync() methods, and keeps Elasticsearch up-to-date with your data when you insert/edit/delete documents with mongoose. Takes an optional options object to tell esmongo the url that Elasticsearch is running at. In options you can specify:

  • url - the url that Elasticsearch is running on. If this is not passed, then the following options are used.
  • host - the host that Elasticsearch is running on (defaults to localhost)
  • port - the port that Elasticsearch is listening on (defaults to 9200)
  • prefix - adds a prefix to the model's search index, allowing you to have separate indices for the same collection on an Elasticsearch instance (defaults to no prefix)

Suppose you have a test database and a development database both storing models in the Cats collection, but you want them to share one Elasticsearch instance. With the prefix option, you can separate out the indices used by esmongo to store your data for test and development.

For tests, you could do something like:

Cat.plugin(esmongo, { host: 'localhost', port: 9200, prefix: 'test' })

And for development you could do something like:

Cat.plugin(esmongo, { host: 'localhost', port: 9200, prefix: 'development' })

This way, you can use the same mongoose collections for test and for development, and you will have separate search indices for them (so you won't have situations like test data showing up in development search results).

Note: there is no need to specify a prefix if you are using separate Elasticsearch hosts or ports. The prefix is simply for cases where you are sharing a single Elasticsearch instance for multiple codebases.

##esmongo.search(searchOptions, callback)

You can use this function to make searches that are not limited to a specific collection. Use this to search across one or several collections at the same time (without making multiple roundtrips to Elasticsearch). The default options are the same as for Model.search(), with one extra key: collections. It defaults to searching all collections, but you can specify an array of collections to search on.

esmongo.search({ collections: [ 'cats', 'dogs' ], query: '*' }, function (err, results) {
	// ...
})

By default, esmongo.search() will use localhost:9200 (the default Elasticsearch configuration). To configure it to use a different url, use esmongo.search.config(options).

##esmongo.search.config(options)

Configure the Elasticsearch url that esmongo uses to perform a search when esmongo.search() is used. options can specify the same keys as Model.plugin(esmongo, options). esmongo.search.config() has no effect on the configuration for individual collections - to configure the url for collections, use Model.plugin().

Example:

esmongo.search.config({ host: something.com, port: 9300 })

#Autocomplete

To add autocomplete functionality to your models, specify which fields you want autocomplete on in the schema:

var CatSchema = new Schema({
    name: { type: String, autocomplete: true },
    age: { type: Number },
    owner: { type: ObjectId, ref: 'Person' },
    nicknames: [ { type: String, autocomplete: true } ]
})

// add the esmongo plugin to your collection
CatSchema.plugin(esmongo)

var Cat = mongoose.model('Cat', CatSchema)

var kitty = new Cat({ name: 'simba' }).save()

Setup the search index using .sync():

Cat.sync(function (err, numSynced) {
  // all cats are now searchable in elasticsearch
  console.log('number of cats synced:', numSynced)
})

Now you have autocomplete on name and nicknames whenever you search on those fields:

Cat.search({ query: 'si', fields: [ 'name' ] }, function (err, searchResults) {
    // any cats having a name starting with 'si' will show up in the search results
})

Running the tests

npm test

License

(The MIT License)

Copyright (c) by Sold. [email protected]

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.