couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Akshat Jiwan Sharma <>
Subject Re: HN thread about CouchDB
Date Tue, 13 Jan 2015 16:44:20 GMT
Would it be a good idea to package couchdb together with couchdb lucene?
When couchdb installs it also fetches and installs couchdb-lucene . Then
whenever a new database is created in couchdb we add an automatic index-all
function in a design document. We could name this design document
_auto_index or something like that. I am talking about this function in

We could also add a configuration parameter for the users to turn off the
indexing if they don't want it.

For users who don't care indexing the fields this would give them the
ability to query in a free form manner. For those who do and don't want to
create these indices they could turn the feature off in the configuration

What I am trying to say here is that if we package couchdb with lucene  by
default then couchdb appears a more complete solution. Even though the
current integration is a single configuration setting away.

On Tue, Jan 13, 2015 at 4:00 PM, Jan Lehnardt <> wrote:

> > On 13 Jan 2015, at 10:38 , Johs Ensby <> wrote:
> >
> > Not surprising, looking at google trends ew decline.
> > That is a pure buzz-index, of course, but what we need to do is to
> connect it to an up-trend for a broad audience.
> > CouchDB needs to be if not the sister, so the cousin of nodejs and
> reactjs or something else that is moving in the right direction.
> I’m not sure this the right approach. We should make sure we work with all
> these things, but I don’t think we should be getting into any family
> relationships with other projects (other than the ones that replicate). The
> surrounding technology comes and goes.
> Best
> Jan
> --
> > J
> >
> >
> >> On 13 Jan 2015, at 10:00, Jan Lehnardt <> wrote:
> >>
> >> Heya (excuse the HN link),
> >>
> >> this is not necessarily something for the weekly news, but I think this
> is a useful summary of how people think about CouchDB in the wild. I’m not
> suggesting this is representative, but it can help guide us in what we want
> to do for our marketing activities, if we are not happy with how people
> think about CouchDB:
> >>
> >>
> >>
> >> I found the comment about design docs most interesting:
> (although I should send this
> to dev@). We should think hard about hiding this detail away from
> end-users.
> >>
> >> Best
> >> Jan
> >> --
> >>
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message