Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Date: Fri, 4 Sep 2015 13:01:10 -0400 (EDT)
From: Joan Touzet <wohali@apache.org>
Reply-To: Joan Touzet <wohali@apache.org>
To: dev@couchdb.apache.org
Cc: marketing@couchdb.apache.org
Message-ID: <22226413.315.1441386069779.JavaMail.Joan@RITA>
In-Reply-To: <0EAA3955-D849-43BE-8E9C-0B3BFA28A3FE@b2w.com>
Subject: Re: CouchDB _rewrite
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Proedurally, CouchDB 2.0 is effectively in feature freeze - we need to
get it out the door, it is far overdue.

Looking at changing basic functionality like _rewrite can come after
2.0 is done, in the 3.0 timeframe.

-Joan

----- Original Message -----
> From: "Johs. E" <johs@b2w.com>
> To: "dev@couchdb.apache.org Developers" <dev@couchdb.apache.org>
> Cc: marketing@couchdb.apache.org
> Sent: Friday, September 4, 2015 8:21:12 AM
> Subject: CouchDB _rewrite
>=20
> Fellow CouchDB enthusiasts,
>=20
> Let me quote a dialogue I had the other day with a colleague on
> Couchapps and _rewrite:
>=20
> > > I would like to know what is so horrible with the vhost/rewrite
> > > of CouchDB
> > You must concentrate all rules in one place, that is totally out of
> > idea =E2=80=98one app =E2=80=93 one ddoc=E2=80=99
> > Capturing mechanics is outrageously ugly and limiting. You can=E2=80=98=
t
> > capture on query, only on path, and in very limiting manner.
> > Obsolete for at least 15 years.
> > Rule lists are flat =E2=80=93 they must be trees, since it=E2=80=98s js=
on, not SQL
> > table of directory with files.
> > It=E2=80=98s all very brittle, error prone and imposes all possible hur=
dles
> > during debug =E2=80=93 no err messages, no log, no validator.
> > And most important: it creates illusion, that it can fit everything
> > =E2=80=93 but it only fits small static-like sites.
> > > Is it something that could be fed to the developers?
> >=20
> > Don=E2=80=98t think anybody of them is interested. This functions assum=
ed
> > obsolete or impractical by the vast majority of community, as I
> > see. And I agree with them.
>=20
> Still with its limitations, I love _rewrite
> You direct the vhost to db/_design/api/_rewrite
> using so-called =E2=80=9Cunsafe=E2=80=9D rewrites, you create an API for =
your many
> databases and their couchapps there.
> It works beautifully.
> That is at Cloudant. I think I learned from an earlier discussion
> that the lack of a =E2=80=9Cdefault vhost=E2=80=9D is a problem outside C=
loudant.
> Now Cloudant does not offer SSL unless you enter into a relationship
> with your local IBM organization and buy a dedicated cluster under a
> std IBM contract, so
>=20
> Of course I would like to see a better rewrite function, my priority
> would be
> A tree structure of rules
> Capture query in the =E2=80=9Cto=E2=80=9D
> That would be a great enhancement to go with version 2.0
>=20
> br
> Johs
>=20
>=20