couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Volker Mische (JIRA)" <>
Subject [jira] Commented: (COUCHDB-837) Adding stale=partial
Date Tue, 27 Jul 2010 10:50:17 GMT


Volker Mische commented on COUCHDB-837:

@Paul: I agree, stale=ok should keep it semantics for off-peak view rebuilding

@Simon: First I prefer not cluttering the query string options. Therefore something like stale=butupdate.
But there's even a bigger problem:
reindex=true doesn't work for me. Think of the default values:
 - no stale, no reindex parameter => normal behaviour, means reindexing
 - stale=ok, reindex=true => return stale, but start reindexing
 - stale=ok, reindex=false => return stale, but don't reindex (current stale=ok behavior)
 - stale=ok, no reindex parameter => and now? should the default reindex value change to
"false" when stale==ok?

@Jira: Either you don't have a preview button, or you are so cluttered I can't find it (which
isn't better)

> Adding stale=partial
> --------------------
>                 Key: COUCHDB-837
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>         Environment: all released and unreleased versions
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>         Attachments: stale_partial.patch
> Inspired by Matthias' latest post, at,
section "Views are updated on read access", I added a new value to the "stale" option named
"partial" (possibly we need to find a better name).
> It behaves exactly like "stale=ok" but after replying to the client, it triggers a view
update in the background.
> Patch attached.
> If no one disagrees this isn't a good feature, or suggest a better parameter value name,
I'll commit.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message