Skip to main content

Description

column_processing configures how Kumo encodes and imputes columns.

na_strategy (Optional)

Use na_strategy to set global N/A handling by semantic type.

Supported Task Types

  • All

Example

This example applies na_strategy="separate" to all numerical columns and na_strategy="most_frequent" to categorical columns.

Supported Semantic Types

  • numerical
  • categorical
  • ID
  • multicategorical
  • text
  • timestamp
  • sequence
Only strategies supported by each semantic type’s encoder are valid. Unsupported combinations fail model plan validation.

encoder_overrides (Optional)

The encoder_overrides field allows you to configure the way Kumo processes your input data and override the encoders that are inferred by Kumo.

Supported Task Types

  • All
Nested fields require exactly four spaces. Each column must be specified with two case sensitive fields:

Example

This example overrides three of the columns in MOVIES table to change the default behavior.
With this example above, Kumo handles the overridden columns as follows:
  • For text column MOVIES.overview, it uses the model "glove.42B" instead of the default "glove.6B". See “GloVe Argument Combinations” section below on this page for available options, and see GloVe project for details.
  • Kumo ignores the column MOVIES.tag_line, and the column has no impact on modelling as it is set to Null().
  • For numerical column MOVIES.budget, Kumo scales numerical values within the range [0, 1] as it is set to "minmax" instead of the default "standard".

Precedence

Kumo applies column_processing overrides in this order:
  1. na_strategy global semantic-type overrides.
  2. encoder_overrides per-column overrides.
If both are set for the same column, encoder_overrides wins.

Supported Encoders

GloVe Argument Combinations

On SPCS, only the GloVe model glove.6B with an embedding size of 50 is currently supported.