The Table Indexer (Labs) node creates a unified, deterministic search index from multiple columns of an input table. Each selected column is defined as an individual indexed field and assigned a semantic data type that determines how the field is interpreted and internally indexed.
Users can dynamically add, reorder, or remove fields within the configuration dialog. Based on the selected semantic data type, the node automatically selects the appropriate internal index structure and storage strategy.
The resulting Table Index Object contains:

• All configured indexed fields
• Their semantic data types
• The corresponding internal index strategies
• Associated structural metadata

This object is designed for downstream use with the Table Index Matcher to enable compound fuzzy matching, structured similarity search, and deterministic entity resolution across multiple fields.

Supported Data Types

Generic Data Types (Current Version)
Used when no domain-specific semantics are assumed.

• Generic – Identity
  For stable identifiers or IDs where structure and exactness dominate. These are typically strings used for identification.
• Generic – Term
  For short, atomic strings such as names, labels, or identifiers.
• Generic – Phrase
  For multi-word text fields such as full names or titles.

Numeric Data Types
Used for strictly numerical columns.

• Numeric – Integer
  For whole-number values without decimal precision (e.g., counts, years, numeric identifiers stored as integers). Treated as numeric values, not free-text.
• Numeric – Double
  For floating-point numbers with decimal precision (e.g., prices, measurements, coordinates). Preserves numeric accuracy during indexing.

Special Field Types

• None – Add Later
  Defines a placeholder field within the index schema. The field is structurally part of the index but not yet actively indexed. It can be activated later using the Index Field Modifier node.
• None – Non-Searchable (Display Only)
  Includes the field in the index strictly as metadata. It does not participate in matching or similarity computation but is returned for contextual enrichment in retrieval results.

Data Types (Coming soon)
The following semantic data types are defined conceptually but are not supported in the current version:
Address Data Types (not supported yet)

• Address – Street
• Address – House Number
• Address – Postcode
• Address – City
• Address – Country

These are intended for structured address components with specialized matching behavior.
Personal Data Types (not supported yet)

• Personal – Email
• Personal – Firstname
• Personal – Lastname

These are intended for identity-related fields with optimized indexing logic tailored to personal data structures.

Options

Index columns

• Input Column: Selects the input table column that will be indexed.
• Index Type: Defines the semantic meaning of the selected input column and how it is treated within the multi-field index.
  This node currently supports Generic and Numeric data types only. Address and Personal types are reserved for future updates.
  
  Generic Data Types (Current Version)
  Used when no domain-specific semantics are assumed.
  • Generic – Identity
    For stable identifiers or IDs where structure and exactness dominate. These are typically strings used for identification.
  • Generic – Term
    For short, atomic strings such as names, labels, or identifiers.
  • Generic – Phrase
    For multi-word text fields such as full names or titles.
  Numeric Data Types
  Used for strictly numerical columns.
  • Numeric – Integer
    For whole-number values without decimal precision (e.g., counts, years, numeric identifiers stored as integers). Treated as numeric values, not free-text.
  • Numeric – Double
    For floating-point numbers with decimal precision (e.g., prices, measurements, coordinates). Preserves numeric accuracy during indexing.
  Special Field Types
  • None – Add Later
    Defines a placeholder field within the index schema. The field is structurally part of the index but not yet actively indexed. It can be activated later using the Index Field Modifier node.
  • None – Non-Searchable (Display Only)
    Includes the field in the index strictly as metadata. It does not participate in matching or similarity computation but is returned for contextual enrichment in retrieval results.
  Data Types (Coming soon)
  The following semantic data types are defined conceptually but are not supported in the current version:
  Address Data Types (not supported yet)
  • Address – Street
  • Address – House Number
  • Address – Postcode
  • Address – City
  • Address – Country
  These are intended for structured address components with specialized matching behavior.
  Personal Data Types (not supported yet)
  • Personal – Email
  • Personal – Firstname
  • Personal – Lastname
  These are intended for identity-related fields with optimized indexing logic tailored to personal data structures.
• Character Mapping: Select the character mapping set to be applied to this column.
• Aliases: Select the alias set you want to apply to the index.
  An Alias Object (created by the Alias Creator node) enables deterministic synonym expansion or canonicalization during indexing.
  When an alias set is applied:
  • Terms may be expanded or rewritten according to alias rules
  • Penalty values influence downstream similarity scoring
  • Deterministic synonym handling improves recall while preserving explainability
  If no alias set is selected, indexing proceeds without synonym expansion.

Views

This node has no views

Workflows

• Address Matching with Multi-Field IndexerKNIME Hub
• Customer Identification via Email Content Matching (Data App)KNIME Hub
• Identity Resolution in Customer Data with Table IndexerKNIME Hub

Links

• No links available

Developers