Skip to content

Commit

Permalink
[DOCS] Removes outdated inference related limitation item. (#1104)
Browse files Browse the repository at this point in the history
  • Loading branch information
szabosteve authored May 27, 2020
1 parent aba4eac commit 6dc7e54
Showing 1 changed file with 0 additions and 25 deletions.
25 changes: 0 additions & 25 deletions docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -135,31 +135,6 @@ feature importance, reducing the amount of training data (for example by
decreasing the training percentage), setting <<hyperparameters,hyperparameter>>
values, or only selecting fields that are relevant for analysis.

[float]
[[dfa-inference-multi-field]]
=== Analytics training on multi-field values may affect {infer}

{dfanalytics-jobs-cap} dynamically select the best field when multi-field
values are included. For example, if a multi-field `foo` is included for training,
the `foo.keyword` is actually used. This poses a complication for {infer} with
the inference processor. Documents supplied to ingest pipelines are not mapped. Consequently,
only the field `foo` is present. This means that a model trained with the field `foo.keyword`
does not take the field `foo` into account.

You can work around this limitation by using the `field_mappings` parameter in the inference processor.

Example:
```
{
"inference": {
"model_id": "my_model_with_multi-fields",
"field_mappings": {
"foo": "foo.keyword"
},
"inference_config": { "regression": {} }
}
}
```

[float]
[[dfa-inference-bwc]]
Expand Down

0 comments on commit 6dc7e54

Please sign in to comment.