Import from AlloyDB for PostgreSQL (Public Preview)

In the Google Cloud console, go to the Agentspace page.

Agentspace

In the navigation menu, click Data Stores.

Click Create data store.

On the Source page, select AlloyDB.

Specify the project ID, location ID, cluster ID, database ID, and table ID of the data that you plan to import.

Click Continue.

Choose a region for your data store.

Enter a name for your data store.

Click Create.

To check the status of your ingestion, go to the Data Stores page and click your data store name to see details about it on its Data page. When the status column on the Activity tab changes from In progress to Import completed, the ingestion is complete.

Depending on the size of your data, ingestion can take several minutes or several hours.

Create a data store.

curl -X POST \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "Content-Type: application/json" \
-H "X-Goog-User-Project: PROJECT_ID" \
"https://discoveryengine.googleapis.com/v1beta/projects/PROJECT_ID/locations/global/collections/default_collection/dataStores?dataStoreId=DATA_STORE_ID" \
-d '{
  "displayName": "DISPLAY_NAME",
  "industryVertical": "GENERIC",
  "solutionTypes": ["SOLUTION_TYPE_SEARCH"],
}'

Replace the following:

• PROJECT_ID: the ID of your project.
• DATA_STORE_ID: the ID of the data store. The ID can contain only lowercase letters, digits, underscores, and hyphens.
• DISPLAY_NAME: the display name of the data store. This might be displayed in the Google Cloud console.

Import data from AlloyDB for PostgreSQL.

  curl -X POST \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  -H "Content-Type: application/json" \
  "https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/dataStores/DATA_STORE_ID/branches/0/documents:import" \
  -d '{
    "alloyDbSource": {
      "projectId": "ALLOYDB_PROJECT_ID",
      "locationId": "LOCATION_ID",
      "clusterId": "CLUSTER_ID",
      "databaseId": "DATABASE_ID",
      "tableId": "TABLE_ID",
    },
    "reconciliationMode": "RECONCILIATION_MODE",
    "autoGenerateIds": "AUTO_GENERATE_IDS",
    "idField": "ID_FIELD",
  }'

Replace the following:

• PROJECT_ID: the ID of your Agentspace project.
• DATA_STORE_ID: the ID of the data store. The ID can contain only lowercase letters, digits, underscores, and hyphens.
• ALLOYDB_PROJECT_ID: the ID of your AlloyDB for PostgreSQL project.
• LOCATION_ID: the ID of your AlloyDB for PostgreSQL location.
• CLUSTER_ID: the ID of your AlloyDB for PostgreSQL cluster.
• DATABASE_ID: the ID of your AlloyDB for PostgreSQL database.
• TABLE_ID: the ID of your AlloyDB for PostgreSQL table.
• RECONCILIATION_MODE: optional. Values are FULL and INCREMENTAL. Default is INCREMENTAL. Specifying INCREMENTAL causes an incremental refresh of data from AlloyDB for PostgreSQL to your data store. This does an upsert operation, which adds new documents and replaces existing documents with updated documents with the same ID. Specifying FULL causes a full rebase of the documents in your data store. In other words, new and updated documents are added to your data store, and documents that are not in AlloyDB for PostgreSQL are removed from your data store. The FULL mode is helpful if you want to automatically delete documents that you no longer need.
• AUTO_GENERATE_IDS: optional. Specifies whether to automatically generate document IDs. If set to true, document IDs are generated based on a hash of the payload. Note that generated document IDs might not remain consistent over multiple imports. If you auto-generate IDs over multiple imports, Google highly recommends setting reconciliationMode to FULL to maintain consistent document IDs.
• ID_FIELD: optional. Specifies which fields are the document IDs.