Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CC8122FC.3438D%mueller@adobe.com>
References: 
 <CAOFYJNakaqw14uaEeWCk2wVo-FGFjgqwNoJjkGZF8Zh-C9BNbA@mail.gmail.com>
 <CC8122FC.3438D%mueller@adobe.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Thu, 20 Sep 2012 20:16:18 +0200
Message-ID: 
 <CAOFYJNZT6s-OdncNAY9SXiH-Jh+P-6fU97HU4-bvfN9Rv4wurw@mail.gmail.com>
Subject: Re: On custom index configuration
To: oak-dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Thu, Sep 20, 2012 at 7:50 PM, Thomas Mueller <mueller@adobe.com> wrote:
> Your are right. To do this efficiently it would require an index on
> [oak:indexed], which would effectively be the same as having the list of
> indexes (and where they are configured) stored at a central place...

Right. The differences to an explicit list are that a node type
index can be used for a lot of other things too and that there's no
need for extra code to maintain such a list.

BR,

Jukka Zitting