Insert Data with Embedding
Embed the data using inference endpoints and then insert the data into the table. The embedding is generated from the embedding source and stored in the embedding target column.
Authorizations
Bearer token authentication. Include the token in the Authorization header as 'Bearer '
Body
If you provide the data to insert into the table in the 'data' field, and set the embedding source and target (using embedding_source and embedding_config), the gateway will automatically generate embeddings for your data and insert the data with the embeddings into the table.
Input limits:
- Max rows in data: 50
- Max bytes for embedding_source text per row: 32KB
Primary Key Generation Rules:
- Format: {Document Id: String}{Record Separator: \RS, ASCII 30}{Chunk Id: Int}
- Document Id: A hash value for duplicate data detection. Recommended length is around 128 characters.
- Record Separator: ASCII 30 character (\u001E)
- Chunk Id: 4-byte unsigned integer (maximum: 2^32-1). Sequential numbers are recommended.
- Do NOT assign the same primary key value (pk) to different chunks. Each pk must be unique per chunk.
List of Data that will be inserted into the table.
Name of the column to get text for embedding. ex) text, metadata, etc.
Embedding type to use. "dense" or "sparse".
Name of the column to store the embedding vector. The embedding vector generated from the embedding source will be added to the column specified by the embedding target. The embedding target column must be a vector column. ex) feature, embedding, etc.