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

elasticsearch-document-transfer

v1.0.2

Published

Simple script to transfer documents between two elasticsearch servers or between indices on the same server.

Downloads

6

Readme

elasticsearch-document-transfer

npm version

Simple Node.js script to transfer documents between two elasticsearch servers or between indices of the same elasticsearch server.

Implementation based on consumer-producer problem.
Since Node.js is single-threaded, producer and consumer cannot simultaneously access the buffer. And hence, as long as the asynchronous nature of Node.js is handled properly, there shouldn't be any issues related to concurrency.

Usage:

  1. Clone the repo.
  2. Run npm install in the directory.
  3. Add config.js using config-sample.js.
    Exercise caution while setting source and target elastic hosts (and while editing this file in general).
  4. (Optional) Set appropriate values in options.js
  5. Run the script
    node index.js

Note:

If options.consume.byFile is set to true, the documents will be written to a file in a format as expected by the bulk API of elasticsearch. The path of file must be specified in config.js.

If options.consume.byElastic is set to true, the documents will be directly added to the target elastic server. The connection details should be present in config.js.