Yes, I could define a syntax for querying the indexing state. My motivation was to get the status of this long-running task where all the others are, for consistency.
Still, it might be handy to have a means to return a detailed summary of the index state anyway, I'll think on that. For now, I'm moving on to separate the indexing process from the searching one and the former to be driven by update notifications for more timely indexing. B. On Tue, Feb 17, 2009 at 1:18 AM, Chris Anderson <[email protected]> wrote: > On Mon, Feb 16, 2009 at 5:00 PM, Robert Newson <[email protected]> > wrote: >> All, >> >> I'm working on couchdb-lucene >> (http://github.com/rnewson/couchdb-lucene) and would like to provide >> feedback on long-running index tasks (which could take minutes >> depending on the amount of change) the same way that compaction and >> view generation feedback is provided. >> >> Specifically, some way to call add_task and update from an external. I >> appreciate that cleanup is currently mediated by Erlang process >> management. Externals would need a remove_task method, which is not >> ideal. >> >> Any thoughts? >> > > The simplest thing for now would be to manage queries for the current > status within your external itself. Since incoming queries already get > passed to it, it's just matter of setting up a status responder > clause. > > > -- > Chris Anderson > http://jchris.mfdz.com >
