[jira] Commented: (COUCHDB-837) Adding stale=partial

["Filipe Manana (JIRA)" <ji...@apache.org>]

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

Filipe Manana commented on COUCHDB-837:
---------------------------------------

Following last @dev mail replies, considered having a new parameter which replaces stale:

update=before  (default value)
update=no  (equivalent to stale=ok)
update=after  (new behaviour)

However it seems that the stale parameter is a replacement for an already deprecated parameter "update". From couch_httpd_view.erl:

parse_view_param("update", _Value) ->
    throw({query_parse_error, <<"update=false is now stale=ok">>});

So, I'll just add "stale=update_after" for the new behaviour.

> 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.