Solr boos issue with Migration to Hybris 1811

[sandeepkumar_nayak2_cgi_c]

Hi All,

We are having solr boosting issue with Hybris 1811.

We recently migrated to 1811 from 6.6.

in 6.6 we had bq param to boost out results and we had boost rules configured.

Old query in 6.6:

fq=allCategories_string_mv:tires&fq={!tag=fk4}(feature\-width_double:205.0)&fq={!tag=fk7}(feature\-ratio_double:55.0)&fq={!tag=fk19}(feature\-diameter_double:16.0)&fq=(((catalogId:"premioProductCatalog") AND (catalogVersion:Online)) OR ((catalogId:"commonProductCatalog") AND (catalogVersion:Online)))&fq=activeFlag_boolean:true&fq=priceValue_vk7_eur_double:*&fq=-priceValue_vk7_eur_double:0.0&fq=premio_boolean:true&fq=stockLevelStatus_1111111111_string:inStock OR stockLevelStatus_1111111111_string:lowStock&q=*:*&defType=edismax&bq=(brand_string_mv:(*GO*^=27.0 OR *DU*^=10.0 OR *FU*^=9.0 OR *SA*^=8.0 OR *DE*^=7.0))☆t=0&rows=20&facet=true&facet.field={!ex=fk13}price_vk7_eur_string&facet.field={!ex=fk2}code_string&facet.field={!ex=fk0}feature-noiseClass_string&facet.field={!ex=fk11}feature-noiseDB_double&facet.field={!ex=fk9}feature-runOnFlatFlag_int&facet.field=categoryPath_string_mv&facet.field={!ex=fk4}feature-width_double&facet.field={!ex=fk10}feature-fuelEfficiency_string&facet.field={!ex=fk14}feature-speedSymbol_string&facet.field={!ex=fk8}feature-season_string&facet.field={!ex=fk15}feature-speedSymbol-display_string&facet.field={!ex=fk1}feature-wetGrip_string&facet.field=allCategories_string_mv&facet.field={!ex=fk18}brand_string_mv&facet.field=feature-construction_string&facet.field={!ex=fk6}feature-loadIndex_double&facet.field={!ex=fk7}feature-ratio_double&facet.field={!ex=fk19}feature-diameter_double&facet.field=freeGiftPromotion_premio_boolean&facet.field={!ex=fk17}category_string_mv&sort=score desc,stockLevelStatus_1111111111_string asc,code_string desc,score desc&facet.mincount=0&facet.limit=500&facet.sort=count

New query:

fq=allCategories_string_mv:tires&fq={!tag=fk4}(feature\-width_double:205.0)&fq={!tag=fk7}(feature\-ratio_double:55.0)&fq={!tag=fk19}(feature\-diameter_double:16.0)&fq=(((catalogId:%22commonProductCatalog%22)%20AND%20(catalogVersion:Online))%20OR%20((catalogId:%22premioProductCatalog%22)%20AND%20(catalogVersion:Online)))&fq=activeFlag_boolean:true&fq=priceValue_vk7_eur_double:[0.01%20TO%20*]&fq=premio_boolean:true&fq=stockLevelStatus_1111111111_string:inStock%20OR%20stockLevelStatus_1111111111_string:lowStock&sort=stockLevelStatus_1111111111_string%20asc,code_string%20desc&q=*:*☆t=0&rows=20&facet=true&facet.field={!ex=fk13}price_vk7_eur_string&facet.field={!ex=fk2}code_string&facet.field={!ex=fk0}feature-noiseClass_string&facet.field={!ex=fk11}feature-noiseDB_double&facet.field={!ex=fk9}feature-runOnFlatFlag_int&facet.field=categoryPath_string_mv&facet.field={!ex=fk4}feature-width_double&facet.field={!ex=fk10}feature-fuelEfficiency_string&facet.field={!ex=fk14}feature-speedSymbol_string&facet.field={!ex=fk8}feature-season_string&facet.field={!ex=fk15}feature-speedSymbol-display_string&facet.field={!ex=fk1}feature-wetGrip_string&facet.field=allCategories_string_mv&facet.field={!ex=fk18}brand_string_mv&facet.field=feature-construction_string&facet.field={!ex=fk6}feature-loadIndex_double&facet.field={!ex=fk7}feature-ratio_double&facet.field={!ex=fk19}feature-diameter_double&facet.field=freeGiftPromotion_premio_boolean&facet.field={!ex=fk17}category_string_mv&facet.mincount=0&facet.limit=500&facet.sort=count

If we add the bq param to the new query also, it does not give the desired result.