Search Profiles
Search profiles map canonical model types to engine-specific types and define naming conventions, analysers, synonym maps, and operational strategies for 6 supported search engines.
Search profiles define how the central model maps to a specific search engine's index schema. Each profile targets one of 6 supported engines and controls type mappings, naming conventions, analyser defaults, synonym maps, custom analysers, and operational strategies. Profiles are stored as .neoarc-search-profile.json files in .neoarc-project/profiles/.
Supported Search Engines
NeoArc Studio supports 6 search engine vendors. Each profile targets exactly one engine.
Profile Structure
A search profile contains several configuration sections. All fields beyond the engine selection are optional and have sensible defaults.
Synonym Maps
Synonym maps define term equivalences for query expansion. Each profile maintains its own registry of synonym maps, referenced by name from property-level search configuration.
Custom Analysers
Custom analysers compose a tokeniser with token filters and character filters. Each custom analyser is registered at the profile level and becomes available in property-level analyser dropdowns alongside the engine's built-in analysers.
interface SearchCustomAnalyzer {
name: string;
tokenizer: string; // Dropdown lookup from engine's built-in tokenisers
tokenFilters?: string[]; // Add/remove list with dropdown lookup per item
charFilters?: string[]; // Add/remove list with dropdown lookup per item
}Operational Settings
Search profiles include operational configuration that governs how indexes are maintained at runtime.
Change Tracking Strategy
Defines how the indexer detects changed documents.
Deletion Strategy
Controls how document deletions are handled in the index.
Index Alias Management
Aliases enable zero-downtime reindexing. The alias pattern uses template variables ({indexName}, {version}, {date}, {environment}).
Index Lifecycle Management
For time-series or retention-sensitive indexes, ILM automates tier transitions and cleanup.
Environment Overrides
A single base profile serves multiple environments. Environment overrides vary operational settings while keeping schema-level configuration (type mappings, analysers, engine) constant across environments.
Engine Features Matrix
Not all features are available on every engine. The matrix below shows which features each engine supports.