Hybris自定义Facet Sort Provider失效问题排查求助

Let's break down the possible issues and fixes step by step—since it works locally and in one test environment, the problem is almost certainly a configuration, indexing, or caching discrepancy in your QA setup:

1. Verify Indexed Property Configuration Sync #

• Double-check that your target Solr Indexed Property in QA has the exact same settings as your working environments:
  • Ensure the facetSortProvider property is pointing to your custom bean ID (not the default defaultFacetValueSortProvider).
  • Confirm the facetSort dropdown is set to CUSTOM (not COUNT or another default option).
  • QA environments often have configuration drift—check if your ImpEx deployments for this property completed successfully, or if someone manually overwrote the settings in the backoffice.

2. Re-build and Refresh Solr Indexes #

• Custom facet sorting often relies on indexed fields that drive the sort logic. If QA's index is outdated or missing these fields, your provider won't work:
  • Run a full index build (not incremental) for the affected Solr core—incremental builds might skip updating the fields your sort provider uses.
  • Use the Solr Admin UI to verify the indexed fields tied to your custom sort exist and have the correct values for test products.

3. Clear All Relevant Caches #

• Caching is a common culprit in QA environments, where old data or logic can persist:
  • Clear Commerce's facet cache and page cache via the Backoffice's Cache Management tool, or run the cache clear command in the Commerce shell.
  • Restart your Solr nodes or clear Solr's query result cache (via Solr Admin > Core > Cache) to eliminate cached sorting logic.

4. Validate Custom Provider Bean Registration #

• Make sure your custom FacetValueSortProvider bean is properly loaded in QA's Spring context:
  • Use the Backoffice's Bean Inspector or a Spring context tool (like JConsole) to confirm the bean exists and isn't being overridden by a default bean.
  • Check the Commerce server logs for errors related to your provider—if it fails to initialize or throws an exception during execution, the system might fall back to the default count-based sorting silently.

5. Do You Need to Modify Solr XML? #

In most cases, no—Commerce's custom facet sort providers handle sorting at the application layer, not directly in Solr. However, if your sort logic relies on Solr-level configurations (like custom sort fields in the request handler), you might need to adjust solrconfig.xml:

• For example, if you're using a Solr sort parameter in your provider, ensure the target field is allowed in the request handler's sort parameter list.
• Only modify Solr XML after ruling out all Commerce-side configuration and indexing issues.

内容的提问来源于stack exchange，提问作者Ricardo Machado