Package com.yahoo.schema.processing

Class MultifieldIndexHarmonizer

java.lang.Object

com.yahoo.schema.processing.Processor

com.yahoo.schema.processing.MultifieldIndexHarmonizer

public class MultifieldIndexHarmonizer
extends Processor

Ensures that there are no conflicting types or field settings in multifield indices, either by changing settings or by splitting conflicting fields in multiple ones with different settings.

Author:

bratseth

Field Summary

Fields inherited from class com.yahoo.schema.processing.Processor

deployLogger, queryProfiles, rankProfileRegistry, schema

Constructor Summary

Constructors

Constructor	Description
MultifieldIndexHarmonizer(Schema schema, com.yahoo.config.application.api.DeployLogger deployLogger, RankProfileRegistry rankProfileRegistry, QueryProfiles queryProfiles)

Method Summary

Modifier and Type	Method	Description
void	process(boolean validate, boolean documentsOnly)	Processes the input search definition by modifying the input search and its documents, and returns the input search definition.

Methods inherited from class com.yahoo.schema.processing.Processor

addField, fail, formatError, info, info, matchingRankSettingsIterator, newProcessException, newProcessException, process, warn, warn

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

MultifieldIndexHarmonizer

public MultifieldIndexHarmonizer(Schema schema,
 com.yahoo.config.application.api.DeployLogger deployLogger,
 RankProfileRegistry rankProfileRegistry,
 QueryProfiles queryProfiles)

Method Details

process

public void process(boolean validate,
 boolean documentsOnly)

Description copied from class: Processor

Processes the input search definition by modifying the input search and its documents, and returns the input search definition.

Specified by:

process in class Processor

Parameters:

validate - true to throw exceptions on validation errors, false to make the best possible effort at completing processing without throwing an exception. If we are not validating, emitting warnings have no effect and can (but must not) be skipped.

documentsOnly - true to skip processing (including validation, regardless of the validate setting) of aspects not relating to document definitions (e.g rank profiles)