If you hit the info url
(http://127.0.0.1:5984/<db>/_fti/_design/foo/<index>), you should see
a uuid and a digest field. e.g,
{"disk_size":10453,"last_modified":"1317250531000","optimized":true,"ref_count":2,"doc_del_count":0,"current":true,"doc_count":110,"digest":"2rwwuvr2ss4re1qounwgcdk3u","uuid":"634437de-e31e-4715-b60d-938069105c70","fields":["default","number"]}
The path to that index is
ROOT_DIR/634437de-e31e-4715-b60d-938069105c70/2rwwuvr2ss4re1qounwgcdk3u/
B.
On 28 September 2011 12:43, Martin Hewitt <[email protected]> wrote:
> Hi all,
>
> We use couchdb-lucene extensively in our projects, but we've hit a point
> where we need to load IndexReaders directly on the relevant indexes, and
> perform operations we can't through the CouchDB REST API.
>
> I've noticed the index folder names don't correspond directly (i.e. clearly)
> to couch databases, and was wondering if there's a way of matching an index
> folder to a database?
>
> Thanks,
>
> Martin
