hi alex please allow me to be confused... maybe the docu is not as clear for someone that is not familiar with the code as it might look for the author ;-)
you say: "indices go under 'oak:index'" "index definition is of type 'oak:queryIndex'" i thought the index content is stored underneath ":index". so, what does 'oak:index' refer to? is it marker or isn't it a marker? and why do you need 'oak:index' if the index definition is identified by the node type 'oak:queryIndexDefinition'? and what happens if someone just adds a node "oak:index" for the sake of it and put's some content in there? kind regards angela On 11/13/13 8:40 PM, "Alex Parvulescu" <[email protected]> wrote: >Hi, > >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 <[email protected]> >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 >> >>
