Github user davisp commented on the pull request:
https://github.com/apache/couchdb-couch/pull/162#issuecomment-210489692
@kxepal for the clustered vs. not dependency, it is slightly odd. However
the changes code is sadly tied into the main couch repo, there's nothing we can
really do to undo that without some pretty awkward contortions just for
purity's sake.
Also, in this case, the mango logic being used is purely functional,
there's no cluster or anything. Its strictly just a "does this json blob match
this other json blob using the mango selector DSL rules" function.
So while I do agree it would be best to have this specific change in a
different app, I'd argue that it's more of that all of this particular changes
code should be in a different app that understands clustered vs not rather than
the hodge podge of things we have now. Until then I wouldn't worry about this
too much since it will work for both clustered and single node.
---
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.
---
