Skip to content

Feature Request: Include UUID index dir name in "info" json response #132

Closed
SonicDeathMonkey opened this Issue Aug 1, 2011 · 3 comments

2 participants

@SonicDeathMonkey

http://127.0.0.1:5984//_fti/_design/foo/

It could be very useful to include the name of the directory of the index in the "info" response json. I realize that the the dir property is defined in the couchdb-lucene.ini, but I only desire the UUID based name (that is appended to the "dir" property value) of the specific dir for the specific index - not the whole path.

When using multiple indexes that change frequently it can be challenging to figure out which one is the dir for a particular index of interest. I could use Luke to actually look at the index to tell, but I'm looking for something that is a little simpler and can possibly be used programattically. In my scenario I'm leveraging Bobo (LinkedIn) for faceting based off the index, but Bobo needs to know the path of the index and with my indexes constantly changing (during development) its hard to keep Bobo synced up. Thanks.

@rnewson
Owner
rnewson commented Aug 1, 2011

Good idea. for now, you could GET /db/_local/lucene for this info.

@SonicDeathMonkey

Thanks, I wasn't aware of that.

Is there a URI to get the specific dir for a specific index function? Basically the next level down from the URI you just provided. Otherwise I still have to figure it out "manually". Or do you have any tips on how to figure it out besides physically looking at the index or making assumptions based off timestamps.

@rnewson
Owner
rnewson commented Aug 1, 2011

There isn't, but it sounds like an easy add. If you're in desperate need look in LuceneServlet, there's an info() method. If not, I'll get to at some point.

@rnewson rnewson pushed a commit that closed this issue Aug 1, 2011
Robert Newson include uuid and digest in index info (closes #132) 25ab23b
@rnewson rnewson closed this in 25ab23b Aug 1, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.