Hi!
Following mailing list discussion [1], I am looking at the
performance of various Mango ways to fetch a bunch of docs.
Following Garren links, I stumbled upon a blog post called
"Understanding Mango View-Based Indexes vs. Search-Based Indexes" [2].
There, the author mentions that:
If users don't know in advance what queries will be executed,
then Mango search-based indexes are the way to go.
This flexibility, however, comes with its own tradeoffs.
That sounds interesting for my use case, so I'm off to Fauxton
creating test docs and trying to declare my first `text` index:
{
"index": {
"fields": [{"name": "test_textindexed", "type": "number"}]
},
"type": "text"
}
To which Fauxton responds with error "text", and a 503 shows up
in the CouchDB log. Looks like I simply don't have the Lucene
engine plugged, but I'm at a loss as to how to enable it in a
post-CouchDB2-release world:
- I couldn't find any mention of it in the docs [3].
- I'm unsure what part of this Cloudant work is now merged
into CouchDB 2 vs. what still needs manual installation,
and my Googling yields mostly old posts/documentation.
* Should I follow the readme of couchdb-lucene? [4]
* Is this 2015 post "Enable FTS in CouchDB" [5] still relevant?
- I'm currently running couchdb2 via the official Docker image.
Should I give klaemo/couchdb-lucene [6] a try?
Thanks for your help :)
[1]
https://lists.apache.org/thread.html/1cd9fa2d063ca0f476d703e4f36fe62d366f9a2fd8910954dcd4798e@%3Cuser.couchdb.apache.org%3E
[2] https://cloudant.com/blog/mango-json-vs-text-indexes/
[3] http://docs.couchdb.org/en/2.0.0/
[4] https://github.com/rnewson/couchdb-lucene
[5] https://developer.ibm.com/dwblog/2015/text-search-apache-couchdb/
[6] https://github.com/klaemo/docker-couchdb-lucene
