Is the bottleneck actual http round trips? Or view building?... If there are no changes to said database... And the vies has been built it will be fast....couchdb does a very good job about this... I'm not sure if it does etaging for views but there is some equivalent.
What is the problem your facing? On Aug 14, 2013 9:31 AM, "Filippo Fadda" <[email protected]> wrote: > No, there is not. This is an information that knows only who wrote the > view map function. I remember you, every document pass through each views, > and only there, inside the map function, you decide to emit or discard the > document from the view. > If a view has been updated, even if the document you have inserted is not > emitted for that view, this could be a bug and you should report it. The > view is an index, and an index shouldn't change if you are not inserting a > new node. > > -Filippo > > On Aug 14, 2013, at 6:12 PM, Daniel Myung wrote: > > > Is there a way or a mechanism or trick or hack of some sort to find out > for > > a given doc I deposit to couch to find out what views it affects? Is > there > > a record of doc ids being operated upon in a design doc reindexing > > operation? > > > > for various reasons, we're looking to reduce the number of view call > round > > trips that our application does on couch, and were looking to cache the > > view response...but invalidation due to *new* docs that could show in the > > view (that we haven't seen) has been preventing us from going further > down > > this route. > > > > Thanks > > > > Dan > >
