Hi, With the recent addition of LucenePropertyIndex we can create a lucene index on a specific type with multiple properties indexed. The queries with full-text like below are served well by this index and help limit the index size * /jcr:root/a/b//element(*, asset)[(jcr:contains(., 'foo'))] order by @jcr:lastModified
But for generic queries on nt:base like /jcr:root/a/b//*[jcr:contains(., 'foo')] order by @jcr:lastModified another index needs to be created. What should be the correct option for creating such an index? Some options that come to mind are: * Create a lucene-property index under the /a/b * Augment the lucene index to also index jcr:lastModified Option 1 looks best to me but we might ultimately end up in a situation where we many indexes defined to cater for specific use cases. Thanks Amit
