Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
This configuration is meant for indexing OAK repository so all the index configurations defined in crx will be used for indexing the JCR nodes. Even though you can define in crx which node paths to index but if you remove all the indexes and just keep /content/products then your repository will slow down terribly. So, I guess for your use case (if you don't want to index JCR nodes in the remote solr) it will be better of to use a remote solr server and index the contents using a custom method which won't use the oak repository indexes. For reference see this project - https://github.com/headwirecom/aem-solr-search
This configuration is meant for indexing OAK repository so all the index configurations defined in crx will be used for indexing the JCR nodes. Even though you can define in crx which node paths to index but if you remove all the indexes and just keep /content/products then your repository will slow down terribly. So, I guess for your use case (if you don't want to index JCR nodes in the remote solr) it will be better of to use a remote solr server and index the contents using a custom method which won't use the oak repository indexes. For reference see this project - https://github.com/headwirecom/aem-solr-search