On Apr 19, 2010, at 6:09 PM, J Chris Anderson wrote: > On Apr 19, 2010, at 12:49 PM, Randall Leeds wrote: > >> Ad-hoc db-wide transformations suddenly strike me as a generic form of the >> compactor. The compactor is an identity update function. It achieves a full >> scan of the db by putting results in a new .couch file. It runs until it has >> caught up to the tail of the current file (using a changes listener) and >> then swaps the files. I believe a good patch here is one that creates a code >> path the compactor can share. >> >> The side bonus is that this implementation is transactional. > > Hmm, interesting thinking. > > As long as we are talking about future compactor features, one that will be > handy once Couch has built-in sharding, is the ability to compact from 1 db > file to 2 (or more) db files.
1 (or more) of which may live on remote nodes. Best, Adam
