Menu
I have a site built using Sitecore 7.5 and Solr 4.7. I am noticing a very strange phenomenon where certain content items are not getting indexed. Here is what is happening.
I have a data template called "Content Page". Most of the content items that are using this data template live in /sitecore/content/Home/Corporate. Things like this:
/sitecore/content/Home/Corporate/About-Us /sitecore/content/Home/Corporate/Careers /sitecore/content/Home/Corporate/Terms-Of-Use There are a few test items that I created that live in /sitecore/content like this:
/sitecore/content/Test-1 /sitecore/content/Test-2 All of these pages are built using the "Content Page" data template. After I rebuild the index and then go to the Solr UI and do a query I can't find any of the items that live beneath the Home node. When I do a query for _templatename:"Content Page" - I only get Test-1 and Test-2 in the results. Does anyone know why this would be happening? It's really odd. I've never seen something where Solr just doesn't index certain items at all. And it seems to be based on where they are in the content tree.
827
In the left column, select 'liferay' under the Core Selector drop-down, and navigate to the query page. Make a query of any content that should be displayed in the Liferay UI. If the appropriate index results are outputted on the right, this confirms that the content is indexed.
Populate an XML schema for SolrThis tool automatically populates Sitecore fields and makes sure all fields that Sitecore needs are present. You can add more fields to this schema by adding fields to the managed-schema file as long as you do not change the system index fields.
Sitecore Experience Platform (XP) has three search frameworks: Content Search, which is used by various components primarily to search and index Sitecore items. xConnect Search, which is used to search and index experience data. Commerce Search, which is used to search and index customers and orders.
Full index takes about 40 hours using DB. There are some factors that might slowing you down: Memory.
According to Pavel Veller on the Sitecore forums, answering a question similar to yours:
First, there are different fallback strategies. Field-level is most likely done via the StandardValuesProvider and yes, you need to have a version in the language for the fallback to kick in. We built a Language Tool wizard in SCORE that can create empty language versions to help in exactly this scenario. You can also do item-level fallback with ItemProvider which will make it appear as if an item had a version in the language even if it doesn't. The good thing about both is that you fallback on the Sitecore API level. Services like search crawlers and publishing all work via those APIs (until you wrote your own, of course) and as a result they all "see" the fallback. Publishing will actually "materialize" the fallback value and the crawler on CD will work with the items and field values as if those were real.
136
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
