Fredhopper Discovery Platform 25.3.0 Upgrade Notes

Fredhopper Discovery Platform 25.3.0 is compatible with the previous release FAS 25.2.0.

Chinese and Korean Language Packs for Lucene

FAS 25.3.0 introduces new language packs for Chinese and Korean languages, which are now available in the search configuration. For more information and configuration options see below:

Lucene Smart Chinese tokenizer

This is an analyzer for Simplified Chinese. Documented here.

Example configuration in business.xml:

<tokenizer-component class="com.fredhopper.search.analysis.advanced.SmartChineseTokenizer">
</tokenizer-component>

No configuration options available for FAS search.

Lucene Korean tokenizer

This is an analyzer for Korean that uses morphological analysis. Documented here.

Example configuration in business.xml:

<tokenizer-component class="com.fredhopper.search.analysis.advanced.KoreanTokenizer">
    <setting name="decompound-mode">MIXED</setting>
    <setting name="output-unknown-unigrams">true</setting>
</tokenizer-component>

Exposed configuration options for FAS search:

IK tokenizer

This is an analyzer that supports Traditional Chinese. Documented here.

Example configuration in business.xml:

<tokenizer-component class="com.fredhopper.search.analysis.advanced.IKTokenizer">
    <setting name="use-smart-segmentation">true</setting>
</tokenizer-component>

Exposed configuration options for FAS search:

Traditional to Simplified Chinese filter

This filter can convert Traditional Chinese to Simplified Chinese characters. Documented here.

Example configuration in business.xml:

<character-filter-components>
    <component class="com.fredhopper.search.analysis.advanced.TraditionalToSimplifiedChineseFilter">
        <setting name="converter-type">TW</setting>
    </component>
</character-filter-components> 

Exposed configuration options for FAS search:

Triggers validation in FAS

FAS can now perform a validation over entity triggers in certain occasions, before adding them to FAS internal rule engine. If a trigger is detected as invalid, the entity is skipped and will not trigger. In order to ensure backward compatibly, a feature switch was introduced under /com/fredhopper/features:

• validate-entity-triggers - if set to true triggers will be validated. In order to disable the feature, this should be set to false. The default value is true.

Example:

<node name="com">
    <map />
    <node name="fredhopper">
        <map />
        <node name="features">
            <map>
                <!--
                If set to `true` FAS will validate entity triggers (currently applied only for location triggers).
                If a trigger is not valid, the entity will not trigger.
                -->
                <entry key="validate-entity-triggers" value="true" />
            </map
        </node
    </node>
</node>