Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Node.js module for Elasticsearch that provides sequences of auto-incrementing integers that can be used to set the id of new documents.
JavaScript
Branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
test
.editorconfig
.gitignore
.jshintrc
.travis.yml
Gruntfile.js
LICENSE
README.md
index.js
package.json

README.md

Elasticsearch Sequence

Build Status Coverage Status Dependency Status Code Climate

es-sequence is a Node.js module for Elasticsearch that provides sequences of auto-incrementing integers that can be used to set the id of new documents.

The sequences are persisted by the Elasticsearch cluster which makes them the last missing feature that maybe prevented you from using Elasticsearch as the sole database in your server stack.

Inspired by the Perl library ElasticSearchX-Sequence by borrowing its approach.

Installation

NPM Stats

This module is installed via npm:

$ npm install es-sequence

es-sequence communicates with the Elasticsearch cluster via the official client library. Since this dependency is injected during runtime you need to install it yourself:

$ npm install elasticsearch

Usage

var sequence = require('es-sequence');
var esClient = require('elasticsearch').Client();

// Initialize es-sequence during server startup
sequence.init(esClient);

// Call get from anywhere
sequence.get('post_id').then(function (id) {

  // Use the id here, e.g. to set the id of a new document:
  esClient.index({
    index: 'blog',
    type: 'post',
    id: id,        // <--
    body: {
      title: 'JavaScript Everywhere!',
      content: 'It all started when...',
      date: '2013-12-17'
    }
  });

});

API

unstable

The API is in the process of settling, but has not yet had sufficient real-world testing to be considered stable. Backwards-compatibility will be maintained if reasonable.

sequence.init(client, [options]) -> Promise

Initialization should be called once during server startup.

client must be a client instance of the official Elasticsearch client library. It is used to set up sequences the first time they are requested and to retrieve new ids through get.

options default to:

{
  esIndex: 'sequences',
  esType: 'sequence'
}

Pass the options accordingly to overwrite the defaults. These parameters are used to store and update documents that represent a sequence in the index esIndex of document type esType.

The index is configured by init for optimal performance. Thus you must use this index for sequences only!

Error Handling

init returns a promise (implemented by Bluebird) which resolves all asynchronous initialization steps. You can use it to handle any errors:

// Promises/A+ compliant use
sequence.init(esClient)
  .then(null, function (error) {
    // Add your error handling code here.
  });

// More expressive alternative provided by Bluebird
sequence.init(esClient)
  .catch(function (error) {
    // Add your error handling code here.
  });

You may catch specific errors originating from Elasticsearch using:

var sequence = require('es-sequence');
var elasticsearch = require('elasticsearch');
var esClient = elasticsearch.Client();

// Promises/A+ compliant use
sequence.init(esClient)
  .then(null, function (error) {
    if (error instanceof elasticsearch.errors.RequestTimeout) {
      // Handle RequestTimeout errors here.
    } else {
      // Handle any other errors here.
    }
  });

// More expressive alternative provided by Bluebird
sequence.init(esClient)
  .catch(elasticsearch.errors.RequestTimeout, function (error) {
    // Handle RequestTimeout errors here.
  })
  .catch(function (error) {
    // Handle any other errors here.
  });

You can choose to ignore the promise. Any early get call will be deferred until the initialization finishes and will fail itself if the initialization had failed. However, I recommend to handle a failure of init during server startup before the server starts accepting incoming requests. Then you may call init again without conflicting with pending get requests (assuming you don't call get during server startup).

sequence.get(sequenceName) -> Promise

Retrieves the next integer of the sequence with the name sequenceName. A new sequence starts with 1. In two consecutive calls the latter will always get a value higher than the former call. However, both values may differ by more than 1 if a node.js server restart occurred in between.

sequenceName can be any string.

Returns a promise (implemented by Bluebird). Call then(...) to pass a callback that will get the retrieved integer as the first parameter:

sequence.get(sequenceName).then(function (id) {
  // Use the id here
});

Error Handling

The promise returned by get will be rejected if retrieving the integer fails for any reason. To handle any error use:

// Promises/A+ compliant use
sequence.get(sequenceName).then(
  function (id) {
    // Called on successful id retrieval
  },
  function (error) {
    // Add your error handling code here.
  }
);

// More expressive alternative provided by Bluebird
sequence.get(sequenceName)
  .then(function (id) {
    // Called on successful id retrieval
  })
  .catch(function (error) {
    // Add your error handling code here.
  });

You may also catch specific errors originating from Elasticsearch as described in the error handling section for init.

Production Readiness

WARNING: I did not use this module in production yet. However, the approach is not too risky.

Travis CI does linting and unit testing for all commits. For unit testing it always uses the latest version of the official client library and a recent if not latest version of Elasticsearch (the database). The current build status is displayed at the top of this document.

You can execute the unit tests for your specific environment:

  1. Make Elasticsearch available on http://localhost:9200 (default port).
  2. Get a local copy of this repo.
  3. Go via the command line to the main folder and execute:
$ npm install
$ npm uninstall elasticsearch
$ npm install elasticsearch@<your version of choice>
$ grunt ci

Change History

  • v0.2.2 (2014-10-15)
    • Updated dependencies
  • v0.2.1 (2014-08-05)
    • Updated dependencies
  • v0.2.0
    • First notable version with a satisfactory API

License (MIT)

Copyright (c) Nicolai Kamenzky (https://github.com/analog-nico)

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.

Something went wrong with that request. Please try again.