Setting Up Embedding Processing
Enabling an Attribute
Running Process Embedding
This step is only required for attributes using the all-MiniLM-L6-v2 or multilingual-e5-small models. Attributes using Adhoc skip this step entirely.
Configuring Top K
The Top K value determines how many similar attribute values the AI retrieves when matching a user's request. For example, if a user asks about "drinks" and Top K is set to 5, the AI will find up to 5 attribute values that are semantically closest to "drinks."
- A higher Top K returns more potential matches, which can improve coverage but may include less relevant values.
- A lower Top K returns fewer, more precise matches.
- Leave this blank to use the system default.
Filtering and Searching
The toolbar at the top of the page provides options to manage large attribute lists:
- Filter (All dropdown): Show only enabled attributes, disabled attributes, or all. Filter by model configured with the attributes.
- Sort: Reorder the list alphabetically.
- Search: Find a specific attribute by name.
Parent/Child Workspace Setup
If your workspace uses a parent/child configuration:
- Embedding processing must be configured on the parent workspace, that is the workspace where the attribute data physically resides in the data warehouse.
- Both parent and child workspaces must have GenAI enabled in their Space Properties.
- Labels and descriptions for the same attributes are configured separately on the child (consumption) workspace.
Best Practices:
- Start with the Adhoc model. It requires no processing step and works immediately. Only switch to another model if your attribute has more than 100,000 unique values.
- Enable selectively. Only enable attributes that users are likely to filter by in natural language. Enabling too many attributes adds no benefit and may slow processing.
- Re-run processing after data loads. If your data changes regularly through ETL, run embedding processing afterward to keep values in sync.
- Test with the Prompt Playground. After configuring embeddings, use the Prompt Playground to verify that the AI is correctly matching user language to actual data values.
- Review Top K settings if you notice the AI is including too many or too few filter values in generated queries.