2023359 - How to create and configure SolrFacetSearch Value Providers

Motivation

In the simplest scenario, it is only necessary to configure the name and type attributes for the indexed property. In this case, for each object that is returned by the indexer query, the used value will come from the attribute in the ordinary Java object (plain old Java object, or POJO) with the same name as the one configured in the indexed property.

Many times this is not enough and you may want to:

• process the value in some way that it may change;
• get the value from a different place, other than the POJO.

When the default behavior is not enough, the solution is to use a value provider. In this trail we will explain in more detail how this process works and how you can create your own value providers.

Default Behavior

By default, even if not explicitly configured, the modelPropertyFieldValueProvider will be used. In this case, the used value will come from the attribute in the POJO with the same name as the one configured in the indexed property.

There are some import details that are worth mentioning:

• This value provider checks if the indexed property is localized and acts accordingly;
• If the POJO is of type VariantProductModel and the result is null, it will return the attribute value from the base product.

Read more...

CPS-SER versions 4.x and 5.x.

SAP hybris Commerce Suite 5.2 ; SAP hybris Commerce Suite 5.3 ; hybris Commerce Suite 4.4 ; hybris Commerce Suite 4.5 ; hybris Commerce Suite 4.6 ; hybris Commerce Suite 4.7 ; hybris Commerce Suite 4.8 ; hybris Commerce Suite 5.0 ; hybris Commerce Suite 5.1

Solr, SolrFacetSearch value provider , KBA , CEC-SCC-COM-SRC-SER , Search and Navigation , How To