Class LocalSearchHintOptions
java.lang.Object
tools.refinery.interpreter.localsearch.matcher.integration.LocalSearchHintOptions
- Since:
- 1.5
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final QueryHintOption
<IAdornmentProvider> A provider of expected adornmentsIAdornmentProvider
.static final QueryHintOption
<ICallDelegationStrategy> Strategy to decide how hints (most importantly, backend selection) propagate across pattern calls.static final QueryHintOption
<Boolean> Whether the search-based query backend is to use registered surrogate queries instead of derived features.static final QueryHintOption
<IFlattenCallPredicate> Predicate to decide whether to flatten specific positive pattern callsIFlattenCallPredicate
static final QueryHintOption
<ICostFunction> Cost function to be used by the planner.static final QueryHintOption
<Integer> static final QueryHintOption
<Boolean> -
Method Summary
-
Field Details
-
USE_BASE_INDEX
-
PLANNER_TABLE_ROW_COUNT
-
PLANNER_COST_FUNCTION
Cost function to be used by the planner. Must implementICostFunction
- Since:
- 1.4
-
FLATTEN_CALL_PREDICATE
Predicate to decide whether to flatten specific positive pattern callsIFlattenCallPredicate
- Since:
- 1.4
-
CALL_DELEGATION_STRATEGY
Strategy to decide how hints (most importantly, backend selection) propagate across pattern calls. Must implementICallDelegationStrategy
.- Since:
- 2.1
-
ADORNMENT_PROVIDER
A provider of expected adornmentsIAdornmentProvider
. The safe default isAllValidAdornments
; however, the generic backend variant may safely useLazyPlanningAdornments
instead.- Since:
- 1.5
-
CONSULT_SURROGATES
Whether the search-based query backend is to use registered surrogate queries instead of derived features.If set to false, the query evaluation will access derived features normally, and take their output at face value. Normally, this should be fine for the search-based backend (as opposed to caching backends), and come at a lower performance cost. Hence the default is false.
Setting this option to true will cause the backend to consult the surrogate query registered for a given feature, if any. Consider this if the default implementation of some features are known to be erroneous, and there are surrogates queries that would provide correct results instead.
- Since:
- 2.9
-