Thank you Vikas for your reply. I am searching using SQL-2 to create queries, those examples don't look familiar to me. When I execute queries here <http://oakutils.appspot.com/generate/index>, nodeScopeIndex is not used so far. Maybe if I dig into that syntax I will see the difference.
Jorge El jue., 28 nov. 2019 a las 13:30, Vikas Saurabh (<[email protected]>) escribió: > On Thu, 28 Nov, 2019, 23:54 jorgeeflorez ., <[email protected]> > wrote: > > > from the reference > < > > https://jackrabbit.apache.org/oak/docs/query/lucene.html#property-definitions > >, > it is not clear to me the difference between the fields analyzed, > nodeScopeIndex, both says that should be set when using *contains* in > queries. But it is not clear the difference or the specific situation, I > think. Any additional reference or explanation is appreciated. > > The details of each field have examples to show the difference. Pasting > from the docs: > ------- > nodeScopeIndex > Control whether the value of a property should be part of fulltext > index. That is, you can do a jcr:contains(., ‘foo’) and it will return > nodes that have a string property that contains the word foo. Example > > //element(*, app:Asset)[jcr:contains(., ‘image’)] > > In case of aggregation all properties would be indexed at node level by > default if the property type is part of includePropertyTypes. However if > there is an explicit property definition provided then it would only be > included if nodeScopeIndex is set to true. > > analyzed > Set this to true if the property is used as part of contains. Example > > //element(*, app:Asset)[jcr:contains(type, ‘image’)] > //element(*, app:Asset)[jcr:contains(jcr:content/metadata/@format, > ‘image’)] > ----------- > > --Vikas > (sent from mobile) >
