You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This example demonstrates how to use Postgres tables as the source for CocoIndex.
6
-
It reads structured data from existing PostgreSQL tables, performs calculations, generates embeddings, and stores them in a separate CocoIndex table.
6
+
It reads structured product data from existing PostgreSQL tables, performs calculations, generates embeddings, and stores them in a separate CocoIndex table.
7
7
8
8
We appreciate a star ⭐ at [CocoIndex Github](https://github.com/cocoindex-io/cocoindex) if this is helpful.
9
9
10
-
This example contains two flows:
10
+
This example contains one flow:
11
11
12
-
1.`postgres_message_indexing_flow`: Read from a simpler table `source_messages` (single primary key), and generate embeddings for the `message` column.
13
-
2.`postgres_product_indexing_flow`: Read from a more complex table `source_products` (composite primary key), compute additional fields and generates embeddings.
12
+
`postgres_product_indexing_flow`: Read from a table `source_products` (composite primary key), compute additional fields like total value and full description, then generate embeddings for semantic search.
14
13
15
14
16
15
## Prerequisites
@@ -25,7 +24,7 @@ Before running the example, you need to:
25
24
26
25
2. Follow the [CocoIndex PostgreSQL setup guide](https://cocoindex.io/docs/getting_started/quickstart) to install and configure PostgreSQL with pgvector extension.
27
26
28
-
3. Create sourcetables `source_messages` and`source_products` with sample data:
27
+
3. Create sourcetable`source_products` with sample data:
0 commit comments