Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Clarifications on CouchDB "index disabling" behavior on view
 errors/exceptions
From: Robert Samuel Newson <rnewson@apache.org>
In-Reply-To: <5696A8E9.8060905@cadensimaging.com>
Date: Wed, 13 Jan 2016 23:05:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D53C3139-9B76-4443-B63D-C0A5F29F8800@apache.org>
References: <5696A8E9.8060905@cadensimaging.com>
To: user <user@couchdb.apache.org>

Hi,

Interesting find. I don=E2=80=99t believe this was ever true, the view =
engine will continue to build in the face of exceptions being thrown for =
every single document it encounters.

B.

> On 13 Jan 2016, at 19:43, Ronan Jouchet =
<ronan.jouchet@cadensimaging.com> wrote:
>=20
> Hi.
>=20
> The CouchDB Guide ( http://guide.couchdb.org/draft/tour.html ) =
mentions that:
>> when a map function fails regularly (due to a missing required field
>> or other JavaScript exception), CouchDB shuts off its indexing to
>> prevent any further resource usage
>=20
> But neither the official doc, nor my Google-fu could provide details:
>=20
> 1. Is this still true as of CouchDB 1.6.1 / 2.0alpha?
>=20
> 2. Which JS errors/exceptions cause a view to be "disabled", exactly?
>=20
> 2.a. In particular, just accessing a non-existent key of a `doc` =
object
>     is not considered an error, right? It evaluates to `undefined`
>     faithfully to vanilla JS behavior, correct? Said differently,
>         `if (doc.species && doc.species =3D=3D=3D 'human')`
>     is equivalent to:
>         `if (doc.species =3D=3D=3D 'human')` , right?
>=20
> 3. How can I "re-enable" a "disabled" view?
>=20
> Thanks :)
>=20
> --=20
> Ronan