Google Cloud SQL for MySQL
Cloud SQL is a fully managed relational database service that offers high performance, seamless integration, and impressive scalability. It offers PostgreSQL, MySQL, and SQL Server database engines. Extend your database application to build AI-powered experiences leveraging Cloud SQL's LangChain integrations.
This notebook goes over how to use Cloud SQL for MySQL
to store vector embeddings with the MySQLVectorStore
class.
Learn more about the package on GitHub.
Before you beginโ
To run this notebook, you will need to do the following:
- Create a Google Cloud Project
- Enable the Cloud SQL Admin API.
- Create a Cloud SQL instance. (version must be >= 8.0.36 with cloudsql_vector database flag configured to "On")
- Create a Cloud SQL database.
- Add a User to the database.
๐ฆ๐ Library Installationโ
Install the integration library, langchain-google-cloud-sql-mysql
, and the library for the embedding service, langchain-google-vertexai
.
%pip install --upgrade --quiet langchain-google-cloud-sql-mysql langchain-google-vertexai
Colab only: Uncomment the following cell to restart the kernel or use the button to restart the kernel. For Vertex AI Workbench you can restart the terminal using the button on top.
# # Automatically restart kernel after installs so that your environment can access the new packages
# import IPython
# app = IPython.Application.instance()
# app.kernel.do_shutdown(True)
๐ Authenticationโ
Authenticate to Google Cloud as the IAM user logged into this notebook in order to access your Google Cloud Project.
- If you are using Colab to run this notebook, use the cell below and continue.
- If you are using Vertex AI Workbench, check out the setup instructions here.
from google.colab import auth
auth.authenticate_user()
โ Set Your Google Cloud Projectโ
Set your Google Cloud project so that you can leverage Google Cloud resources within this notebook.
If you don't know your project ID, try the following:
- Run
gcloud config list
. - Run
gcloud projects list
. - See the support page: Locate the project ID.
# @markdown Please fill in the value below with your Google Cloud project ID and then run the cell.
PROJECT_ID = "my-project-id" # @param {type:"string"}
# Set the project id
!gcloud config set project {PROJECT_ID}
Basic Usageโ
Set Cloud SQL database valuesโ
Find your database values, in the Cloud SQL Instances page.
Note: MySQL vector support is only available on MySQL instances with version >= 8.0.36.
For existing instances, you may need to perform a self-service maintenance update to update your maintenance version to MYSQL_8_0_36.R20240401.03_00 or greater. Once updated, configure your database flags to have the new cloudsql_vector flag to "On".
# @title Set Your Values Here { display-mode: "form" }
REGION = "us-central1" # @param {type: "string"}
INSTANCE = "my-mysql-instance" # @param {type: "string"}
DATABASE = "my-database" # @param {type: "string"}
TABLE_NAME = "vector_store" # @param {type: "string"}
MySQLEngine Connection Poolโ
One of the requirements and arguments to establish Cloud SQL as a vector store is a MySQLEngine
object. The MySQLEngine
configures a connection pool to your Cloud SQL database, enabling successful connections from your application and following industry best practices.
To create a MySQLEngine
using MySQLEngine.from_instance()
you need to provide only 4 things:
project_id
: Project ID of the Google Cloud Project where the Cloud SQL instance is located.region
: Region where the Cloud SQL instance is located.instance
: The name of the Cloud SQL instance.database
: The name of the database to connect to on the Cloud SQL instance.
By default, IAM database authentication will be used as the method of database authentication. This library uses the IAM principal belonging to the Application Default Credentials (ADC) sourced from the envionment.
For more informatin on IAM database authentication please see:
Optionally, built-in database authentication using a username and password to access the Cloud SQL database can also be used. Just provide the optional user
and password
arguments to MySQLEngine.from_instance()
:
user
: Database user to use for built-in database authentication and loginpassword
: Database password to use for built-in database authentication and login.
from langchain_google_cloud_sql_mysql import MySQLEngine
engine = MySQLEngine.from_instance(
project_id=PROJECT_ID, region=REGION, instance=INSTANCE, database=DATABASE
)
Initialize a tableโ
The MySQLVectorStore
class requires a database table. The MySQLEngine
class has a helper method init_vectorstore_table()
that can be used to create a table with the proper schema for you.
engine.init_vectorstore_table(
table_name=TABLE_NAME,
vector_size=768, # Vector size for VertexAI model(textembedding-gecko@latest)
)
Create an embedding class instanceโ
You can use any LangChain embeddings model.
You may need to enable the Vertex AI API to use VertexAIEmbeddings
.
We recommend pinning the embedding model's version for production, learn more about the Text embeddings models.
# enable Vertex AI API
!gcloud services enable aiplatform.googleapis.com
from langchain_google_vertexai import VertexAIEmbeddings
embedding = VertexAIEmbeddings(
model_name="textembedding-gecko@latest", project=PROJECT_ID
)
Initialize a default MySQLVectorStoreโ
To initialize a MySQLVectorStore
class you need to provide only 3 things:
engine
- An instance of aMySQLEngine
engine.embedding_service
- An instance of a LangChain embedding model.table_name
: The name of the table within the Cloud SQL database to use as the vector store.
from langchain_google_cloud_sql_mysql import MySQLVectorStore
store = MySQLVectorStore(
engine=engine,
embedding_service=embedding,
table_name=TABLE_NAME,
)
Add textsโ
import uuid
all_texts = ["Apples and oranges", "Cars and airplanes", "Pineapple", "Train", "Banana"]
metadatas = [{"len": len(t)} for t in all_texts]
ids = [str(uuid.uuid4()) for _ in all_texts]
store.add_texts(all_texts, metadatas=metadatas, ids=ids)
Delete textsโ
Delete vectors from the vector store by ID.
store.delete([ids[1]])