Contents
Why does Sitecore send content to SOLR for indexing?
This means that Sitecore will send the content of all fields to Solr for indexing, expect the ones that you explicitly exclude from indexing (Opt-out). This may be ok for small solutions, but for large solutions, this will cause indexes to become very large and indexing to be CPU heavy and time consuming.
How are computed fields used in Sitecore 7?
Computed fields allow you to index values calculated while indexing, such as the URL of each item. Before you read this blog post, please read the Sitecore 7: Introduction blog post linked in the list of resources at the end of this page.
How to make Solr collections work with SolrCloud?
To make this work with SolrCloud, you’ll need to use the Sitecore.ContentSearch.SolrProvider.SwitchOnRebuildSolrCloudSearchIndex index type. The idea is that you have two Solr collections for every index together with two aliases. The main alias points to one of the indexes and a rebuild alias points to the other index.
Where can I find the managed schema for Solr?
Look into the managed schema stored in your Solr instance/cluster to ensure your config changes has been applied properly. You may also find solr.WordDelimiterGraphFilterFactory very useful for stemming things like product names, trade marks, phone numbers, SKU numbers etc.
Why do I get a success message in Sitecore?
You’ll get a “success”-message in Sitecore regardless if your update snippets are correct and stored in Solr or not. So make sure you read the managed schema file in the Solr UI to verify that the changes have actually been stored. Sitecore may show a success message even when the managed schema update are not applied in Solr.
What’s the difference between a Solr core and a collection?
Worth noticing is that Solr “cores” are called “collections” in SolrCloud. A “core” in SolrCloud is just a shard or replica of a collection. To make Sitecore work well with Solr, you should use switching indexes.
Is there a way to replace the Sitecore processor?
You can either replace the existing Sitecore.ContentSearch.SolrProvider.Pipelines.PopulateSolrSchema.PopulateFields processor, given that you provide the necessary functionality, or add your own processor. I found it easier to replace the existing one as I found a couple of errors in the built in one that I needed to address anyway.
Is there a way to fix missing fields in Solr?
When you do that, you will notice in your Crawler.log errors that certain fields are missing from your sitecore_master_index and sitecore_web_index. To fix this, go to your Solr instance and on the left select Core Selector. First pick your master_index and click on Schema.