[ 
https://issues.apache.org/jira/browse/COUCHDB-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094085#comment-13094085
 ] 

Paul Joseph Davis commented on COUCHDB-1266:
--------------------------------------------

In fact, the more I think about it, I don't see why we wouldn't just create a 
single JSON blob for each task, then all clients can do whatever it is they 
want to do with the data. I'd also get rid of things like progress and instead 
focus on allowing clients to do their own calculations and display.

> Add stats field to _active_tasks
> --------------------------------
>
>                 Key: COUCHDB-1266
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1266
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>             Fix For: 1.2
>
>
> 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 "status");
> 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:
> http://dl.dropbox.com/u/25067962/active_tasks_stats.png
> Patch at:
> https://github.com/fdmanana/couchdb/compare/task_stats.diff

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to