On Fri, Oct 3, 2014 at 10:57 PM, benjamin.bast...@gmail.com < benjamin.bast...@gmail.com> wrote:
> Yeah, what Paul said is correct. > > As far as replication, you would be able to manually mediate a view > replication with the view changes feed, but there's no built-in > functionality to do it for you. Unless you're talking about the > view-filtered replication, which will be optimized if the view is sequence > indexed. > > It is in rcouch. So it was about to reuse the code ... I do think that such change requires a ticket for those who want to track at least, but this quite out of topic so just let's talk about this specific change. How does key filtering work with such things? Or isn't it part of the view change any more? If it is what would be the result? On an operational part such changes imply that views changes are about getting index operations on a doc. Which is conceptually different that than getting changes on an index. Maybe we could have both, but I think having index changes is also interesting independently of having index operations on a doc. It is also covering 2 different usages. Imo having doc index operations could be done on another resource point. Thoughts? - benoit.
