Databases
StackOverflow2013
Postsdbo
POIs there a good indexing / search engine for Node.js?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs there a good indexing / search engine for Node.js?
    text
    copied!<p>I'm looking for a good <em>open source</em> (with LGPL or a permissive license) indexing engine for a node.js application, something like Lucene. I'm looking for in-process indexing and search and am not interested in indexing servers like Sphinx or Solr.</p> <p>I am not afraid to create bindings for a C/C++ library either so I'm open to those kind of suggestions as well.</p> <p>So far I've found</p> <ul> <li><strong>node-clucene</strong> which doesn't seem to be actively maintained anymore (and has several open issues)</li> <li>I could create my own binding for <strong>CLucene</strong> but it seems to be quite sparsely maintained and its current version is also quite behind the Java Lucene</li> <li><strong>Apache Lucy</strong> which seems to be designed for the purpose of creating bindings for dynamic languages, but so far they don't have node bindings (nor a C API) and I haven't found any docs about creating bindings. I also didn't find any benchmarks about its performance.</li> <li><strong>node-search</strong> which seems to be abandoned</li> <li><strong>jsii</strong> which seems to be still a prototype and is also abandoned</li> <li><strong>fullproof</strong> which is only intended to run in a web broswer</li> <li><strong>lunr.js</strong> which seems to only allow serializing the whole index, so isn't scalable</li> </ul> <p>I could "roll my own", but I'd prefer to use an already existing solution.</p> <p><em>EDIT: Why I'm not interested in a standalone index server:</em> I use a fast in-process key-value store database, so it'd be quite a waste having to go out of process for querying.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload