5

There is absolutely no harm in doing this. sitecore_master_index root is set to /sitecore and all the other indexes which operates on master database have their roots set to one of the /sitecore item descendants. It works just fine. You can create another index with /sitecore as a root without any issues. I can imagine having a bucket with different type ...


5

sitecore_core_index is not used for CD server. The rest is correct. You can check search indexes requirements in a scalable environment here: https://doc.sitecore.com/developers/91/platform-administration-and-architecture/en/the-search-indexes-required-in-a-scalable-environment.html


5

Something like this has worked for me. Beyond the boosting, the important part is to have the exact match Or the loose match. exactPredicate.Or(loosePredicate); That will build the proper SOLR query. { var parentPredicate = PredicateBuilder.True<ContentPageSearchModel>(); var exactPredicate = PredicateBuilder.False<ContentPageSearchModel>...


5

Some of the steps that can be followed to increase the performance of Solr indexing are: Limit the items getting into Solr: You can limit the number of items that are getting indexed by changing the <Root>/sitecore</Root> parameter in Sitecore index configuration file. Stored Vs Indexed: Not all fields needs to be both Stored as well as ...


4

To rebuild indexes from sitecore powershell you can use below script which will re-index all indexes one by one using namespace Sitecore.ContentSearch $indexes = [ContentSearchManager]::Indexes foreach($index in $indexes){ Write-Host "Re-indexing started " $index.Name $index.Rebuild([IndexingOptions]::ForcedIndexing); Write-Host "Re-indexing ...


4

Finally figured out how to do this. Firstly, you want to make sure you start the Refresh/Rebuild properly. What I mean by that is that if you want to be able to identify the right crawler related to a given Indexing Job, you will need to tag the Indexing Job with some ID. You can do that by adding a Message to the job when starting it. Job myRefreshJob =...


4

This is how text fields work, it's a tokenized search.. If you are looking for an exact string match, you should be using returnType="string" in your index configuration. Beware as well that you should not be using _t in your code as that hardcodes the Solr field type. You should also change that in your code to just [IndexField("email")]. This should be all ...


3

The solution mentioned in Dan Sinclair's comment worked to fix this issue. Thanks Dan! DELETE FROM [Core].[dbo].[Properties] WHERE [Key] LIKE '%_LAST_UPDATED_TIMESTAMP%'


3

In my case, I'm always doing this to fix that : Make sure your Sitecore configured properly for SOLR within \App_Config\Sitecore\ContentSearch Check your connectionstrings for SOLR is configured properly or not Access SOLR admin (with browser, make sure it's https) to check whether it's on or not If it's on, check again if your configured index matches with ...


3

You could call the Azure Search Rest API directly to query the index-catalog Example request: GET xxx.search.windows.net/indexes/index-catalog/docs?search=*&$filter=sitecorename eq 'sitecore_web_index' Result: { "value": [ { "@search.score": 1, "key": "SITECORE_WEB_INDEX-SEARCH", "sitecorename": "...


3

After investigating I found that this error occured in Avatar facet. It looks like sitecore indexer bug. This issue happens when image for avatar has a big/medium resolution. Image data (byte[]) is big and as I understand there are some limits in JsonReader or somewhere else. After many attempts I found that 128x128 jpeg image is OK and error dissappears, ...


2

The indexing strategies are controlled by the configuration files in App_Config and how they are updated/rebuilt is controlled by the indexing strategies: https://doc.sitecore.com/developers/91/platform-administration-and-architecture/en/index-update-strategies.html I would recommend having a look at /sitecore/admin/showconfig.aspx for that environment and ...


2

This is vague, but let me try to interpret what you're asking. You have many languages in your solution, but you'd like to just index 2 of those languages -- you DO NOT want the other languages to be indexed. If this is the case, I'd suggest storing content for those 2 languages into their own custom index that only defines those languages. This "domain ...


2

I think you are misunderstanding how a computed field and the storage type works. The storageType has nothing to do with the content being added to the index. It just controls whether the content is stored along with the indexed values. If you store the content too, then you can retrieve the content out of the index. If you don't, then you can only search ...


2

Technically this is possible. You can copy the index files from the CM server and deploy that out to the CD servers. But, there are concerns with doing that. I am making the assumption that you have this question because you want to have a zero downtime deployment: The CD servers will still want to re-index as part of any publish operation, so you may need ...


2

This is expected behavior. You are looking at it in Luke. SOLR encodes the datetime fields so it can handle sorting/filtering in a better way than pure Lucene. If you look at the an item in the SOLR viewer, with a date field. You will find the date is perfect. I asked the same question a little while ago. The issue is don't look at Luke. Look at the SOLR ...


2

Sitecore has been very specific that Lucene should not be used in scaled out environments. This is because every CD may have a different index, and demonstrate the issue that you are reporting. Sitecore's own documentation says: You must use Solr if you have a scaled environment. The recommendation to fix this issue is to install Solr and have all CD's ...


2

Sitecore configs are case sensitive. Your config contains returntype with lowercase t character. It should be returnType with capitacl case T. <fieldNames hint="raw:AddFieldByFieldName"> <field fieldName="contentheading" returnType="text"/> <field fieldName="contentintro" returnType="text"/> <field fieldName="startdate" ...


2

The obvious answer is to use the Web index for any (site) search related functionalities. There are also other site search like functionalities. You could think of a news articles or product (,or any other) overview, especially if you're including some kind of filtering mechanism. Other then that the index could be used for any functionality that require ...


2

There used to be ExcludeField method in ProviderIndexConfiguration in older Sitecore version. It was just calling DocumentOptions.AddExcludedField as Matthew Dresser wrote in his comment. At some point it was marked as obsolete and finally it was removed. In Sitecore 9.1.0 rev. 001564 dll method ExcludeField is no longer there. AddExcludedField of ...


2

I think you have the change the returnType. That is now string, which is not multiValued.. change that to stringCollection. Keep the multiValued as well (although I'm not sure it is even needed) - but I'm quite sure the returnType needs to indicate the multivalue (too). The fact that your error mentioned a _s suffix indicates that a single value should be ...


1

For this purpose, I would use the iframe field type, which is IMO the most flexible solution for custom field types. You can find more information about the iframe field type here: Cascading Droplist field in Sitecore https://trnktms.com/2017/04/06/sitecore-iframe-field-basics/ The advantege is that you have the full control of the presentation and stored ...


1

It seems rubber-ducking with the community helped me solve the problem I have had for 3 days. The solution: (it seems you have to do BOTH, although I am not 100% certain) Delete and manually re-create index-catalog Delete all references to the index in the properties table in the core database I believe that the reason why I had the error was partly due ...


1

Based on the latest information it looks like the issue may be related to a bug that was fixed in Sitecore 9.2 (release notes): ​​In Azure Search, the SwitchOnRebuildEventRemote event is shared through the EventQueue of the Web database instead of the system EventQueue. To determine if this affects you, answer the two questions below: Is the web ...


1

I have this working through the below code. Basically I'm doing the following: Splitting the search term into words and getting the entire length Building one predicate for entire search term together and doing a boost by (length * length) Building predicates for each of the word and then doing an Or with the above predicate var tokens = request.SearchTerm....


1

I have implemented the same functionality with the following code in sitecore 9 update 2 if (sortBy !="date") { string termFreq = GetTermFrequency("suggestiontitle_t", searchText); var query = context.GetQueryable<SearchResultModel>() .Where(i => i.NoIndex == false && (i....


1

The Solution The issue is with this line of code: using (var index = ContentSearchManager.GetIndex(indexName)) Remove its using block and it will work: var index = ContentSearchManager.GetIndex(indexName); Why? When the using block exits it will call .Dispose() on the index which stops indexing: From Sitecore.ContentSearch.AbstractSearchIndex public ...


1

Usually this is due to an invalid Azure Search connection string, check for a typo in the service endpoint or in the associated parameters.


1

Sounds like you are missing the needed IFilter to index pdf content. Check https://doc.sitecore.com/developers/91/platform-administration-and-architecture/en/index-pdf-files.html for the information on 9.1: The Sitecore Content Search API uses the native Microsoft Windows IFilter interface to extract the text content from media files for indexing. ...


1

Option 1. Just wrap your code in SiteContextSwitcher: using (new SiteContextSwitcher(Factory.GetSite("YOUR_COMMERCE_SITE_NAME"))) { // get price here } Option 2. Review Sitecore.Commerce.Engine.Connect.Search.Crawlers.SellableItemsCrawler, not SitecoreItemCrawler. It does request to CE to get list of Sellable Items with all required price information,...


Only top voted, non community-wiki answers of a minimum length are eligible