This would be a nice feature. I should have a look into Jackrabbit indexer code, but time is missing.
But you gave me another idea, maybe I should simulate indexation by copying values into the parent's node into a special pre-defined property. It makes me change writing procedures and queries, but should speed up the search operations. Thank you, Frank Le 2010-05-25 à 5:51 AM, Ard Schrijvers a écrit : > 2010/5/20 François Cassistat <[email protected]>: >> Hi, >> >> is it possible to configure indexation so path-based properties tests gets >> faster in a similar way aggregate is used for full-text search? > > You have some indexing_configuration.xml where you can define some > indexing rules, but queries like: 'where there is a child node that > has propA=valA' are not possible to index more efficient. It also make > sense that it is hard to do this in a general jcr repository: If you > can query fast on properties of child nodes, you should also be able > to query fast on properties of child nodes 5 levels deeper. > > But, if you have a very clear content model, you might want to hook in > your extended indexer capable of indexing child node properties on, > say, your notion of a 'Document'. This is however far from trivial, > > Regards Ard > >> >> >> Frank >> >>
