Many thanks for the answer.The main drawback for that solution is that TeamA and TeamB don't need the same index fields. Moreover, TeamB index definition contains a list of excluded paths. Merging both indexes in one penalizes TeamB as:The reindex process takes longer.The index management is more di...

Hello,Thanks for the answer. Sure, that document is my bedtime book  and according to it: "1. Q: For precise index selection is it advised always use native query? * A: if you can't manage to have the query engine select a specific index based on cost tweaks (recommended way), native query is your ...

Hello,I'm currently working with AEM 6.2 and I would like to know if I can select (deliberately) a lucene index to perform different queries. For example, imagine 2 different teams working on these paths:TeamA works on /content/dam/stuff and defined an index named TAIndexTeamB works on /content/dam/...

Hello,I am Alvaro from Spain, a newcommer to AEM. The keywords that describe me are: Solr, Elastic, Lucene and Java.