Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Vector database target properties

Vector database target properties

In advanced mode, you can write vectors to a vector database such as Pinecone. You can configure the target properties, advanced properties, and target fields.

Target properties

The following table describes the vector database target properties:
Property
Description
Connection
Name of the target connection.
Alternatively, you can define a parameter, and then specify the connection in the
mapping
task.
Target Type
Target type, either single object or parameter.
Object
Name of the target object.
Operation
Target operation. You can use only upsert.
Update Columns
The fields to use as temporary primary key columns when you upsert target data. When you select more than one update column, the
mapping
task uses the AND operator with the update columns to identify matching rows.
If you generate an ID within the mapping, the ID is dynamic and might not be consistent with existing IDs in the vector database. If a generated ID matches an existing ID in the vector database, the Target transformation replaces the row in the vector database, but the vector might not correspond to the same data.
For more information about the target properties, see the help for the appropriate connector.

Advanced properties

The following table describes the advanced properties:
Property
Description
Batch Size
Number of operations for the vector database to process at the same time.
Namespace
Namespace in the vector database where you want to store the vectors.

Target fields

The following table describes the target fields that a Target transformation might write to a vector database:
Property
Description
Vector ID
Vector identifier to store in the vector database. The ID helps to quickly access the vector representation for efficient storage, indexing, and retrieval operations.
To create vector IDs, you can use the UUID_STRING function with no arguments in an Expression transformation or you can use a Sequence Generator transformation that uses a shared sequence across all mappings that load data to the same index in the vector database.
Vector
Array of doubles that represents the vector embedding.
You can use a Vector Embedding transformation to create vector embeddings.
Metadata
Metadata to write to the vector database as a struct. Includes all incoming fields except for the vector and vector ID fields. The metadata field contains a list of key-value pairs in JSON format.
The target fields can differ based on the vector database. For more information about target fields, see the help for the appropriate connector.

0 COMMENTS

We’d like to hear from you!