Hybris 6.5版本下如何排除Solr分面搜索结果？

It’s frustrating when your facet-hiding code doesn’t kick in—let’s break down the most likely reasons why your current approach in FacetSearchQueryPopulator isn’t working, plus actionable fixes:

1. Your Code May Be Incomplete #

Looking at your snippet, it appears to be missing closing braces for the for loop and conditional check. Syntax errors or unclosed blocks can cause your logic to fail silently.

Fix: #

Ensure your code is properly structured:

for(FacetField facet : facetList) { 
    if("price".equals(facet.getField()) && isHidePrices()){
        continue; 
    }
    FacetInfo facetInfo = new FacetInfo(facet.getField(), facet.getFacetType()); 
    facets.put(facet.getField(), facetInfo); 
} // Close the for loop

2. Your Populator Runs After the Default One #

Hybris uses a list of populators to build the facet search query. If your custom populator executes after the default FacetSearchQueryPopulator, the default will re-add the price facet you tried to skip.

Fix: #

Adjust the order in your Spring config to run your populator first (lower order values execute earlier):

<bean id="customFacetSearchQueryPopulator" class="com.yourpackage.facetsearchquerypopulator">
    <property name="order" value="10"/> <!-- Default populator typically uses order 100 -->
</bean>

<bean parent="facetSearchQueryPopulatorList">
    <property name="list">
        <list>
            <ref bean="customFacetSearchQueryPopulator"/>
            <ref bean="defaultFacetSearchQueryPopulator"/>
        </list>
    </property>
</bean>

3. isHidePrices() Isn’t Returning true When Expected #

Double-check if your visibility logic is actually triggering. Context-specific conditions (like user group, storefront, or session state) can fail silently without logging.

Fix: #

Add debug logging to confirm the condition fires:

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

private static final Logger LOG = LoggerFactory.getLogger(YourPopulatorClass.class);

for(FacetField facet : facetList) { 
    if("price".equals(facet.getField())){
        LOG.debug("Price facet found. Should hide? {}", isHidePrices());
        if(isHidePrices()){
            LOG.debug("Skipping price facet");
            continue; 
        }
    }
    FacetInfo facetInfo = new FacetInfo(facet.getField(), facet.getFacetType()); 
    facets.put(facet.getField(), facetInfo); 
}

Check your Hybris logs to verify these messages appear when you expect the price facet to be hidden.

4. The Facet Field Name Doesn’t Match "price" #

Hybris often uses Solr field names like priceRange (for range facets) instead of plain "price", depending on your facet configuration. Using the wrong name means your skip condition never matches.

Fix: #

Verify the exact field name in the Backoffice:

• Go to Facet Search > Configurations
• Select your Solr configuration
• Navigate to the Facets tab
• Find your price facet and check the Field Name value

Update your code to use this exact name (e.g., if("priceRange".equals(facet.getField()))).

5. Facet Configuration Enforces Visibility #

Even if your populator skips the facet, the facet’s Backoffice configuration might force it to be visible.

Fix: #

In the same facet configuration screen:

• Ensure the Visible checkbox isn’t locked to true
• Check that any Dynamic Visibility Groovy scripts aren’t overriding your code

6. Try a More Reliable Approach: FacetFilterStrategy #

Hybris provides a dedicated FacetFilterStrategy interface to filter facets before display—this is the recommended method for controlling facet visibility.

Example Implementation: #

public class PriceFacetFilterStrategy implements FacetFilterStrategy {
    private static final Logger LOG = LoggerFactory.getLogger(PriceFacetFilterStrategy.class);
    private boolean hidePrices;

    @Override
    public List<FacetField> filterFacets(List<FacetField> facets) {
        if (!hidePrices) {
            return facets;
        }
        List<FacetField> filteredFacets = new ArrayList<>();
        for (FacetField facet : facets) {
            if (!"priceRange".equals(facet.getField())) { // Use your actual field name
                filteredFacets.add(facet);
            } else {
                LOG.debug("Filtering out price facet");
            }
        }
        return filteredFacets;
    }

    // Inject this value from your service or configuration
    public void setHidePrices(boolean hidePrices) {
        this.hidePrices = hidePrices;
    }
}

Configure in Spring: #

<bean id="priceFacetFilterStrategy" class="com.yourpackage.PriceFacetFilterStrategy">
    <property name="hidePrices" value="#{yourVisibilityService.isHidePrices()}"/>
</bean>

<bean id="yourFacetSearchConfig" parent="abstractFacetSearchConfig">
    <!-- Other config properties -->
    <property name="facetFilterStrategy" ref="priceFacetFilterStrategy"/>
</bean>

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