[
https://issues.apache.org/jira/browse/COUCHDB-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-640:
--------------------------------------
Component/s: JavaScript View Server
Description:
It was mentioned on IRC that if someone restores a database without restoring a
view then there's nothing that detects if the view is still valid. Ie, it may
reflect an update_seq that the restoration lost.
In the check for kicking off a view update we should check if there is an
incompatibility between what's been calculated in the view vs what the db
update sequence is at. The current logic will just ignore and return the
invalid view data (because of how stale=ok works which is good).
Should be an easy bug to fix if anyone's interested. The code should be pretty
contained to couch_view.erl and couch_view_group.erl
Affects Version/s: 0.11
Summary: Detect when a view is not valid for a database (was:
Detect when a view)
> Detect when a view is not valid for a database
> ----------------------------------------------
>
> Key: COUCHDB-640
> URL: https://issues.apache.org/jira/browse/COUCHDB-640
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
> Affects Versions: 0.11
> Reporter: Paul Joseph Davis
>
> It was mentioned on IRC that if someone restores a database without restoring
> a view then there's nothing that detects if the view is still valid. Ie, it
> may reflect an update_seq that the restoration lost.
> In the check for kicking off a view update we should check if there is an
> incompatibility between what's been calculated in the view vs what the db
> update sequence is at. The current logic will just ignore and return the
> invalid view data (because of how stale=ok works which is good).
> Should be an easy bug to fix if anyone's interested. The code should be
> pretty contained to couch_view.erl and couch_view_group.erl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
