Hi Josh, This sounds like a question for hardcore search guys. Maybe you might have more luck asking this question on one of the Jackrabbit lists ?
Regards Felix Joshua Oransky schrieb: > Ok, > > Basically what I need is the reverse of what index aggregating does > in JCR. I need to aggregate content from PARENT nodes onto my child > nodes, so that the child is searched as if it has all the content of the > whole hierarchy. > > Is this possible, and how do I do it? > > -Josh > > > On Oct 1, 2008, at 2:46 PM, Alexander Klimetschek wrote: > >> Hi Josh, >> >> something like >> >> //california//element(*, my:House) >> >> where my:House is the node type identifying houses could do the trick. >> Or if you have a fixed hierarchy (houses are two levels under the >> state) and no specific node type for houses, this would work: >> >> //california/*/* >> >> Regards, >> Alex >> >> On Wed, Oct 1, 2008 at 7:52 PM, Joshua Oransky <[EMAIL PROTECTED]> >> wrote: >>> I have a hierarchy that is utilizing inheritance; that is, my app >>> consolidates all information on an entire hierarchy on a single node. >>> >>> This means that information is spread across the hierarchy, but I >>> want my searches to come up with only the end node... >>> >>> For example, take this hierarchy: >>> >>> /country >>> /state >>> /city >>> /house >>> >>> I want my searches to only return house nodes, but the house node >>> doesn't contain information about the city, state, or country. Is >>> there a >>> way to collapse the hierarchy for searches, so that a search for, say, >>> "California" returns all the houses in California, not the California >>> node? >>> >>> Thanks! -Josh >>> >> >> >> >> -- >> Alexander Klimetschek >> [EMAIL PROTECTED] > >
