couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1266) Add stats field to _active_tasks
Date Tue, 30 Aug 2011 23:52:09 GMT


Filipe Manana commented on COUCHDB-1266:

I see what you mean now Paul.

I still think the progress field should be given by couch and is one of the fields people
care most about.

As for Futon, specially for replication tasks, I see all (or most) of those stats meaningful
for the normal user. Other than displaying the json object, I don't see a way to display these
fields which are not common for all tasks, I guess someone specialized on UIs would find a
much better way.

> Add stats field to _active_tasks
> --------------------------------
>                 Key: COUCHDB-1266
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>             Fix For: 1.2
>         Attachments: alternate-api.patch
> This proposal is simply to add a "stats" field to the _active_tasks results. This field
can be an arbitrary JSON value and each task can set it to whatever is appropriate for it.The
following patch also defines some basic stats for the existing tasks:
> 1) database compaction - # changes done, total changes, # of revisions copied, # of attachments
copied and progress (an integer percentage, same as what is exposed in the existing text field
> 2) view compaction - # of ids copied, total number of ids, # of kvs copied, total number
of kvs and progress
> 3) view indexing - # changes done, total changes, # inserted kvs, # deleted kvs, progress
> 4) replication - # missing revisions checked, # missing revisions found, # docs read,
# docs written, # doc write failures, source seq number, checkpointed source seq number, progress.
> A screenshot of Futon with 3 different tasks:
> Patch at:

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message