Skip to main content
Production use of this feature is available for specific editions only. Contact our sales team for more information.
Public preview Snowpark Container Prompt is an orchestration component that lets you host your large language models within your Snowpark Container Services. This topic presumes you have a strong knowledge of Snowpark Container Services and have already set up your Snowpark container. To learn more about creating an app, read our guide How to create a Snowpark Container Services application. Matillion sends your data to your Snowflake warehouse as a user-defined function (UDF). A unique ID is assigned to the UDF sent to Snowflake Container Services. Matillion does not retain this ID once your data has been sent to Snowflake Container Services. Your application that is running in your Snowpark container will receive the UDF data as a JSON payload in the format of an array of arrays where each sub-array represents a row of data: 
{
    "data": [
                [0, "System Prompt", "User Prompt", {"Input Column Name": "Input Column Value"}, {"metadata key": "metadata value"}]
    ]
}
Your app should be set up to receive the data in this format. You may wish to read the following Snowflake documentation before getting started with this component.

​
Properties

​
Name
string
required
A human-readable name for the component.
​
Database
drop-down
required
The Snowflake database. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
​
Schema
drop-down
required
The Snowflake schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
Service
drop-down
required
Select your Snowpark Container Services service. The services available in this list will depend on the selected database and schema.
​
Endpoint Name
drop-down
required
Select the endpoint name representing the TCP network port that your application exposes.
​
Endpoint Path
string
required
The path to your selected endpoint.
​
Metadata
column editor
Optionally supply key:value metadata pairs such as top_p, n, max_tokens, and so on to be sent to the large language model.Ensure that no personal data, sensitive data, export-controlled data, or other regulated data is entered as metadata in the specification file.
​
Database
drop-down
required
The Snowflake source database. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
​
Schema
drop-down
required
The Snowflake source schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
Table
drop-down
required
An existing Snowflake table to use as the input.
​
Key Column
drop-down
required
Set a column as the primary key. Join the results back to the input table.
​
Limit
integer
Set a limit for the numbers of rows from the table to load. The default is 1000.
​
User Context
text editor
Provide your prompt. When Output Format is TEXT, this property is where you must specify all of the questions that you wish the LLM to provide answers to.Prompts should define the following information:
  • A persona. Who or what should the model impersonate when contextualizing their generative responses?
  • A context. Contextualize the situation for the model to enhance its responses.
  • A tone. What kind of language do you want the model to use?
Providing an example output may improve performance.
​
Inputs
column editor
required
Select the source columns to feed as input to the prompt component.
  • Column Name: A column from the input table.
  • Descriptive Name: An alternate descriptive name to better contextualize the column. Recommended if your column names are low-context.
​
Output Format
drop-down
required
Choose TEXT or JSON. Choosing JSON will activate an additional property, Outputs.
​
Outputs
column editor
required
JSON only.Define the output columns the prompt component will generate.
  • Output: Key of a key:value JSON pair. For example, an output might be “review_score”.
  • Context: Text that defines the output you expect the model to provide—that is, some task for the model to perform. For example, “Give a score between 0 and 10 on the level of satisfaction you feel in the user’s review where 0 is completely dissatisfied and 10 is extremely satisfied.” You may wish to use this parameter to configure the tone of the model (where applicable).
​
Database
drop-down
required
The Snowflake destination database. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
​
Schema
drop-down
required
The Snowflake destination schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
Table
string
required
The new Snowflake table to load your prompt output into. Will create a new table if one does not exist. Otherwise, will replace any existing table of the same name.
​
Create Table Options
drop-down
required
  • Replace if Table Exists: The pipeline will run despite the table already existing. The table will be recreated.
  • Fail if Table Exists: If the table already exists, the pipeline will fail to run.
  • Append: If the table already exists, any new rows (records) will be added to the table without modifying or deleting existing rows. If the table does not exist, it is created and any new rows are inserted.
Snowflake only:This component uses the CREATE OR REPLACE clause. When using the REPLACE clause, it also applies the COPY GRANTS clause. When you clone or create a new object (such as a table, view, schema, or database) from an existing one, the new object doesn’t automatically inherit the original’s grants (privileges). However, with the COPY GRANTS clause, you can seamlessly transfer object-level privileges from the source object to the new one. This helps maintain consistent access control and simplifies permission management when cloning or recreating objects. For more information, read Snowflake COPY GRANTS.
​
Enable RAG
boolean
required
Click Yes to enable Retrieval-Augmented Generation (RAG). Using RAG optimizes an LLM output by invoking an authoritative knowledge base outside of the LLM’s initial training data sources. By using RAG, you can extend an LLM’s capabilities to specific domains, such as your organization’s documentation, without needing to retrain the model.Defaults to No.
​
Pretext
text editor
required
Add text to your LLM prompt before the RAG data is listed, thus instructing the LLM what to do with the RAG data. For example, you might wish to use RAG to search relevant documentation snippets to answer a question.Example:“Use any of the following documentation snippets in your response, if relevant:”
​
Search Column
drop-down
required
Choose a column in the source table that contains a search term for the vector database. The value is then taken from that column and a vector search is performed. For example, a column value might be a user question such as “How do I log in?”. A search is then performed on the vector database using the value string, which will return N number of relevant data. N is defined by the Top K parameter, further down.If your vector database contained vectors created from chunks of text documentation, in this scenario the RAG data returned may include the chunk “to log in, click on the key button in the top right and enter your username and password”. This data is then inserted into the llm prompt to help provide relevant context.
​
Embedding Provider
drop-down
required
The embedding provider is the API service used to convert the search term into a vector. Choose either OpenAI or Amazon Bedrock. The embedding provider receives a search term (e.g. “How do I log in?”) and returns a vector.Choose your provider:
​
OpenAI API Key
drop-down
required
Use the drop-down menu to select the corresponding secret definition that denotes the value of your OpenAI API key.Read Secrets and secret definitions to learn how to create a new secret definition.To create a new OpenAI API key:
  1. Log in to OpenAI.
  2. Click your avatar in the top-right of the UI.
  3. Click View API keys.
  4. Click + Create new secret key.
  5. Give a name for your new secret key and click Create secret key.
  6. Copy your new secret key and save it. Then click Done.
​
Embedding Model
drop-down
required
Select an embedding model.Currently supports:
  • text-embedding-ada-002
  • text-embedding-3-small
  • text-embedding-3-large
​
Vector Database
drop-down
required
Select a vector database to use.Currently supports Pinecone and Postgres.
​
Pinecone API Key
drop-down
required
Use the drop-down menu to select the corresponding secret definition that denotes the value of your Pinecone API key.Read Secrets and secret definitions to learn how to create a new secret definition.
​
Pinecone Index
string
required
The name of the Pinecone vector search index to connect to. To retrieve an index name:
  1. Log in to Pinecone.
  2. Click PROJECTS in the left sidebar.
  3. Click a project tile. This action will open the list of vector search indexes in your project.
​
Pinecone Namespace
string
The name of the Pinecone namespace. Pinecone lets you partition records in an index into namespaces. To retrieve a namespace name:
  1. Log in to Pinecone.
  2. Click PROJECTS in the left sidebar.
  3. Click a project tile. This action will open the list of vector search indexes in your project.
  4. Click on your vector search index tile.
  5. Click the NAMESPACES tab. Your namespaces will be listed.
​
Top K
integer
required
The number of results to return from the vector database query.Between 1-100.Default is 3.
​
Data Lookup Strategy
drop-down
required
Select the data lookup strategy. Pinecone only stores the vector associated with text data, and a JSON metadata blob. While the text data can be stored in the metadata blob, size limitations can affect coverage—for example when a user has a larger blob of text to be converted to a vector.
  • Raw data in metadata: Choosing this option adds an additional property, Data Path, to provide the path to text data within the metadata JSON blob.
  • Table details in metadata: Database, schema, and table information is used in the metadata to look up the text data in your warehouse table.
​
Data Path
string
required
Set the path to the data in the metadata JSON blob.Default is data.