jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Parvulescu <alex.parvule...@gmail.com>
Subject Re: Security Concerns wrt Index Definitions
Date Wed, 13 Nov 2013 19:40:59 GMT

I'd like to chime in on the docs observation.

Indices go under 'oak:index'. An index definition node is of type
'oak:queryIndexDefinition', there's no constraint on the name.
You also have a bunch of examples showing just that on various index
implementations [0].

I don't see where the confusion may come from.

[0] http://jackrabbit.apache.org/oak/docs/query.html

On Wed, Nov 13, 2013 at 7:16 PM, Angela Schreiber <anchela@adobe.com> wrote:

> hi jukka
> >The idea behind the oak:index child node for index definitions was
> >that you could place them close to the content being indexed.
> just re-read the query.md and it states at the very beginning:
> "Query Indices are defined under the `oak:index` node."
> given the fact that we ship oak with some default indexes that
> are all located at /oak:index i fear that everyone will just add
> there indexes there.
> only later the documentation states:
> "To define a property index on a subtree you have to add an index
> definition node that:
>  * must be of type `oak:queryIndexDefinition` [...]"
> but doesn't state that the node must be named 'oak:index'.
> that's a bit confusing and you can't enforce that name unless
> you specify a mixin such as proposed by tobi.
> kind regards
> angela

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