Hi! I'm in bit of a dead end, and what i've read in the documentation here has not helped me much.
I'm using the suggester OOTB service to get results, and right now it's working but it's fetching suggestions from all kinds of different unwanted places.
The server on which this AEM instance will run will host multiple projects, so I need to have it suggest stuff only from my project, "content/myProject1".
It's currently suggesting from "content/myProject1", "content/myProject2", "content/myProject3" and so on.
I've went to oak-index and opened the cq:PageLucene, and I tried the following:
added content/myProject1 as an object in multistring queryParams
added content/myProject1 in queryParams and includedPaths too
added content/myProject2 in excludedPaths
After each change I reindexed and tried again. No matter which route I go on, and for no matter what input I give, i only get an empty array as a response. That can't be right, and i'm not sure what am I doing wrong.
cqPageLucene index /oak:index/cqPageLucene/indexRules/cq:Page is indexing all cq:Page type of node in JCR. It means that page in all projects that you are hosting in AEM will be indexed. There is not needs to add paths to projects.
That been said, it's unclear what is your overall goal. Are you using queries that are leveraging some custom properties, and that is why you are in need to update cqPageLucene?
In addition to what Leo mentioned, if you are talking about AEM Projects and not pages.
There is an index named "cqProjectLucene" that is used for any queries triggered on the "cq:Project" mixin type nodes. Example, when you go under theprojects.html page and try to trigger a search, AEM will trigger the query below:
select [jcr:path], [jcr:score], * from [cq:Project] as a where contains(*, 'test') and isdescendantnode(a, '/content/projects')
Using the explain query tool from AEM, I can see this query is using the "cqProjectLucene" index which has the lowest cost for this kind of query.