Originally I intended for other indexers to be callback behaviors loaded into couch_index. Since writing that code though I've come to the conclusion that its not the best approach. If you want to collapse it somewhere I'd collapse it back into couch_mrview and undo some of the abstractions.
As to collapsing it into the main couch application that makes no sense seeing as the entire point of pulling it out was to remove the dependency of the main couch application on indexers. On Thu, Jan 9, 2014 at 4:25 PM, Benoit Chesneau <[email protected]> wrote: > Hi all, > > Maybe Paul can answer. But I am wondering why we have couch_index in its > own folder. For me it is quite difficult to see it separated from couchdb > (even with the supervision). While couch_mrview fit well in its own > repository since one can consider to replace it by another kind of index. I > am thinking we should put it back in the main couch app. > > Thoughts? > > - benoit
