You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Robert Newson <ro...@gmail.com> on 2009/02/17 02:00:54 UTC
external access to task_status methods?
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?
B.
Re: external access to task_status methods?
Posted by Robert Newson <ro...@gmail.com>.
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 <jc...@apache.org> wrote:
> On Mon, Feb 16, 2009 at 5:00 PM, Robert Newson <ro...@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
>
Re: external access to task_status methods?
Posted by Chris Anderson <jc...@apache.org>.
On Mon, Feb 16, 2009 at 5:00 PM, Robert Newson <ro...@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
Re: external access to task_status methods?
Posted by Antony Blakey <an...@gmail.com>.
On 17/02/2009, at 11:30 AM, Robert Newson wrote:
> Any thoughts?
Maybe do it as an Erlang plugin, so you don't need to modify the
external channel protocol?
Antony Blakey
--------------------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
Man will never be free until the last king is strangled with the
entrails of the last priest.
-- Denis Diderot