[ https://issues.apache.org/jira/browse/COUCHDB-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099967#comment-13099967 ]
Paul Joseph Davis commented on COUCHDB-1270: -------------------------------------------- @Bob, Totally see your point on being overly specific. That was one of my biggest worries when starting this work. I had GeoCouch updated to work with a slightly older version of this patch (that I'll rebase shortly) and have played with a few other types of indexers for giggles. One thing I can say is that even when an indexer might not have a user controllable compaction, it seems common enough that it should be exposed for when it exists. > Rewrite the view engine > ----------------------- > > Key: COUCHDB-1270 > URL: https://issues.apache.org/jira/browse/COUCHDB-1270 > Project: CouchDB > Issue Type: Improvement > Components: JavaScript View Server > Reporter: Paul Joseph Davis > Attachments: 0001-Minor-changes-for-new-indexing-engine.patch, > 0002-Create-the-couch_index-application.patch, > 0003-Create-the-couch_mrview-application.patch, > 0004-Remove-the-old-view-engine.patch > > > The view engine has been creaky and cluttered. As shown by GeoCouch, adding > new indexers basically involves copying the entire view engine and hacking > the parts that are different. In short, the opposite of good engineering. > Over the last couple weeks I've refactored the view engine and reimplemented > the map/reduce view engine. These changes are 100% internal and no external > behavior has changed. Performance is just a tiny bit better than trunk. I did > do some playing trying to improve view update times and there are some dances > we could do, but for the time being I wanted to keep the same general > architecture for updates so that the changes are minimal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira