couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1270) Rewrite the view engine
Date Mon, 12 Sep 2011 14:46:10 GMT


Jan Lehnardt commented on COUCHDB-1270:

Just thinking releases, I'd like to branch 1.2.x sooner than latter. Do you recon this is
a good patch to go into 1.2.x or should it go into trunk after branching? I'm happy to branch
1.2.x so you can commit this to trunk any time. I think I'd feel more comfortable having this
simmer in trunk for 1.3.x (given that I'd like start work on the 1.2.x release about now,
not commenting on the quality of the patch, just is time-new-ly-ness and the general and conservative
thinking, if this ramble makes any sense :)

> Rewrite the view engine
> -----------------------
>                 Key: COUCHDB-1270
>                 URL:
>             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:


View raw message