[
https://issues.apache.org/jira/browse/COUCHDB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892617#action_12892617
]
Chris Anderson commented on COUCHDB-837:
----------------------------------------
Last bikeshed perspective from me:
stale=ok for current behavior, and stale=lazy or stale=freshen for the one that
updates the views in the background.
I'm not that into a separate param for this, (I've already said I think the
current behavior is a bug), because update_index makes zero sense on a
non-stale query.
I liked 'ok' because it was non-committal, I think 'freshen' or 'lazy'
maintains that vibe, while being descriptive of the effect.
I'm gonna leave this up to Filipe to implement, it's his choice since he's
writing the patch.
> Adding stale=partial
> --------------------
>
> Key: COUCHDB-837
> URL: https://issues.apache.org/jira/browse/COUCHDB-837
> 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
> http://www.paperplanes.de/2010/7/26/10_annoying_things_about_couchdb.html,
> 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.
