[GitHub] couchdb-fabric pull request #72: Send a message when filtering a changes row

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/couchdb-fabric/pull/72


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fabric pull request #72: Send a message when filtering a changes row

[davisp]

GitHub user davisp opened a pull request:

https://github.com/apache/couchdb-fabric/pull/72

Send a message when filtering a changes row

We managed to miss this change during the great merge as it was a
confusing mess in the cloudant/fabric repository. Its obvious in
hindsight once you see that we have a
`fabric_view_changes:handle_message/3` clause to handle the message.

COUCHDB-3178

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-fabric 
3178-fix-fabric-rpc-filtered-changes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-fabric/pull/72.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #72


commit 6006bc6c8e491456c186950cdc12257036142b16
Author: Paul J. Davis 
Date:   2016-10-04T20:12:38Z

Send a message when filtering a changes row

We managed to miss this change during the great merge as it was a
confusing mess in the cloudant/fabric repository. Its obvious in
hindsight once you see that we have a
`fabric_view_changes:handle_message/3` clause to handle the message.

COUCHDB-3178




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---