Github user nickva commented on the pull request:
https://github.com/apache/couchdb-couch/pull/162#issuecomment-222195609
@colinskow that implies some kind of persistence. The selector passed in a
change feed request is active only in the context of the POST request. There
could be multiple such concurrent requests. After request is finished, there is
no history preserved of previous request.
Or were you thinking about a long / continuous request, and while it is
returning data back to the user, a document which passed the filter and was
returned before, was updated to no longer pass the selector. But there is
nothing to tell the user about it. So perhaps have something in the change feed
saying "this document passed the selector before but no longer does".
That is an interesting case then. If document is deleted we return it with
`"_deleted":true`, is it reasonable to have something like
`"_selector_failed":true`? I am not sure about this. You might want to take
this up on the couchdb mailing list. This looks like an API change then and
needs a better discussion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
