couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "Why are all Views in a single Index" by BenjaminYoung
Date Fri, 17 Feb 2012 14:30:58 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Why are all Views in a single Index" page has been changed by BenjaminYoung:
http://wiki.apache.org/couchdb/Why%20are%20all%20Views%20in%20a%20single%20Index?action=diff&rev1=2&rev2=3

Comment:
added jchris' tweet about back refs

  }}}
  Here view1 and view2 have exactly the same map function. If they were in different design
documents, there would be two b-trees (in two different index files) for exactly the same
data. Now, if they are in a single design document, we use one b-tree only, but we save disk
space and update time by only updating one btree instead of two. Of course, this is easy only
because we use one single index file for a design document with multiple views.
  
+ == Other Reasons: ==
+ ||<tablewidth="100%"> {{https://si0.twimg.com/profile_images/1611440478/IMG_0049_normal.jpg|jchris}}
||'''jchris'''<<BR>>@bigbluehat @fdmanana also a combined index file can keep
a  single index of back refs from docids to rows, for invalidating old  rows<<BR>>
[[https://twitter.com/jchris/status/169514764693803010|2/14/12 3:14 PM]] ||
+ 

Mime
View raw message