Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of robert.newson@gmail.com
 designates 209.85.220.20 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=xzxnIP8ZHNTlDMac/ftiwuy5CRT9KhzrO7zwzX1H/kdaOZL++s375KSyf8tJIrmN7l
         QBGlmcNQjufencPyONoF+zxPhVRwJogCKXf2FhTK6TXHJGmanzn69sN3lPy70VeyV8kF
         7ydiVZd8Dti9TTiTQWWV8+cavGeNTXtMOHEMY=
MIME-Version: 1.0
In-Reply-To: <e282921e0902161718q7c75902ewc1bc7296fec701d6@mail.gmail.com>
References: <46aeb24f0902161700l1d288959y9a41aea46f4ccf9f@mail.gmail.com>
	 <e282921e0902161718q7c75902ewc1bc7296fec701d6@mail.gmail.com>
Date: Tue, 17 Feb 2009 01:21:49 +0000
Message-ID: <46aeb24f0902161721r4a2f480cmdaaabd1603e8235c@mail.gmail.com>
Subject: Re: external access to task_status methods?
From: Robert Newson <robert.newson@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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 <jchris@apache.org> wrote:
> On Mon, Feb 16, 2009 at 5:00 PM, Robert Newson <robert.newson@gmail.com> 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
>