New answers tagged

0

I'm not sure when it changed but in Sitecore 10.x you now need to change the returnType parameter which is used for whether the field gets tokenized or not. For example string does not get tokenized but text does. <field fieldName="firstlastname" returnType="string"> Sitecore.Fields.FirstLastNameComputedField, Circle.Fields</...


3

This is a long known issue with Solr, where if a field is stored / has analyzers / is tokenized, it returns incorrect results. This is vaguely mentioned on the documentation here. It was blogged about years ago by Rich Seal here who said that you can add a copyField with parameters indexed="true" stored="false" and then sort by that field....


0

Just be sure, can you validate the java memory you are allocating for your solr instance ? I had similar issues, where I fixed it by allocating more java memory. You can easily do it by adding this line in this file path\to\your\solrInstance\solr-6.6.0\bin\solr.in.cmd : set SOLR_JAVA_MEM=-Xms2g -Xmx2g I am using 2g in local, but 4 in production environment. ...


1

I wound up using the approach recommended by @AnnaGevel and added a boosted keywords field. While I don't think this is quite as precise as the Query Elevation Component would be, it's maintainable by content editors without needing to write a custom add-on.


0

do NOT put double quotes in :) ""


Top 50 recent answers are included