couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Senthilkumar Peelikkampatti <>
Subject Re: Hovercraft query_view enhancement
Date Mon, 25 Jan 2010 03:43:53 GMT
Thanks Chris & Grempe...
I am able to get include_docs working by following
couch_httpd_view.erl. before jumping into details, I want to explain
why hovercraft is matter for me. I am using couchdb for my web
application which purely erlang based. I don't see the benefit using
http/REST in my app as the benefit of load balancing/caching etc
outweighs performance gain of 6-7 times (whopping 700%) and it is
sweet of erlang as it excels distributed processing why can't utilize
that? I plan to have read & write process group so that it can be
utilized for master/slave and master-master setup. My app currently
using couchbeam but I am planning to migrate to hovercraft. Hovercraft
is one of the mechanism whcih pulls erlangers into couchdb and hence I
strongly recommend to keep grooming hovercraft along with couchdb.

Back to Hovercraft, I just tweaked make_map_row_fold_fun to call
couch_httpd_view:view_row_obj and include doc is now working but as
Joscha found, end_key is not used and I try to use it (used
couch_httpd_view:make_key_options) but I am not able to make it work
properly as the results are skewed and I will try to find out more.
Thanks for stopping by....


On Sun, Jan 24, 2010 at 12:51 AM, Chris Anderson <> wrote:
> On Sat, Jan 23, 2010 at 10:29 PM, Glenn Rempe <> wrote:
>> I would probably bring this up on the list for ideas
>> from the developers.
>> And thanks for the kind words, glad I could help.  :-)
>> Glenn
> I've been keeping an email tab open to this thread for a while trying
> to find time to reply.
> I'm glad that so many people are using Hovercraft to query CouchDB
> from Erlang. It's often not the right tool for the job (but when you
> do need turn Couch into an IMAP server backend or something custom,
> it's a good start).
> I'm a firm believer that people who actually use and hack on code,
> should be the ones maintaining it. I haven't used Hovercraft in anger
> in almost a year, but that doesn't mean it's not decent code for you
> to use. I just haven't needed it.
> So... I propose that anyone who's using Hovercraft, should get in
> touch with each other (maybe through this thread) and figure out a way
> to push the project forward, bless a github repo, etc. I'd be happy to
> help by setting up a Google Group, but I think it'd probably be better
> if one of you set that up.
> I'm not throwing my hands up and walking away from the project by any
> stretch. If circumstances arise that I need Hovercraft, I'll
> definitely use it. And if anyone has code questions, please corner me
> on IRC so I can help. But I'm not actively hacking on Hovercraft or
> using it lately so I think the project will be healthier if people who
> use it are driving it.
> Thanks,
> Chris
>> On Thu, Jan 21, 2010 at 3:28 PM, Senthilkumar Peelikkampatti <
>>> wrote:
>>>  I started again working on enhancing hovercraft for greater cause :)
>>> and all existing hovercraft API is working now(thanks to grempe who
>>> completed where I left in github). Besides, I wanted to add 1)
>>> query_view with all the kind of options available in http REST API, 2)
>>> all_docs with include _doc support etc. With the current state of
>>> query_view, when I try  to include_doc, it is not returning the
>>> complete document. I looked at query_view and I can do lot of magic
>>> with RowCollectorFun or  ViewFoldFun in general but I am afraid if it
>>> is right place to do. I briefly look at couch_httpd_view on how it is
>>> handled for REST but before doing anything weired I wanted to reach
>>> out couchdb dev to know how/which api I need to access to get view
>>> filter functionality?
>>> My next step would be to come up with consistent hash based or erlang
>>> pg2 and pool based framework to do multi node communication. before
>>> that I wanted to make sure some of the functionality in hovercraft is
>>> working similar to http API.
>>> --
>>> Regards,
>>> Senthilkumar Peelikkampatti,
>> --
>> Glenn Rempe
>> email                 :
>> voice                 : (415) 894-5366 or (415)-89G-LENN
>> twitter                : @grempe
>> contact info        :
>> pgp                    :
> --
> Chris Anderson

Senthilkumar Peelikkampatti,

View raw message