Skip to content

Proxyv2 #1373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cjac merged 4 commits into from
Jan 23, 2026
Merged

Proxyv2 #1373

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
89b5c70
Update the incompatibility notice to alert users not to use CloudSQL …
Jul 29, 2025
21761db
Added the feature to re-use hive-metastore in cloud-sql-proxy for MySQL
Jan 22, 2026
4fcc12c
Update cloud-sql-proxy/cloud-sql-proxy.sh
dilipgodhia Jan 23, 2026
6b35f3b
Update cloud-sql-proxy/README.md
dilipgodhia Jan 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions cloud-sql-proxy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,18 @@ metadata on a given Cloud SQL instance.

**⚠️ IMPORTANT COMPATIBILITY NOTICE ⚠️**

**Cloud SQL Proxy V2 script has been upgraded to use the latest binary client that is compatible with MySQL 8.4 and some newer Cloud SQL features.**
**The Cloud SQL Proxy script has been upgraded to use the V2 binary client by default, which is compatible with MySQL 8.4 and some newer Cloud SQL features.**

Specifically:
* **MySQL 8.4 has updated its security model that were incompatible with the earlier version of this CloudSQL Proxy script.**
* **MySQL 8.4 has an updated security model that was incompatible with the earlier version of this Cloud SQL Proxy script.**

However, if you choose to use Cloud SQL Proxy V1 (see options below):
* **MySQL 8.4's updated security model is incompatible with Cloud SQL Proxy V1.**
* **Enabling "Shared CA"** or **"Customer-managed CA"** features for any Cloud SQL database (including older MySQL versions and PostgreSQL) will break connectivity with Cloud SQL Proxy V1.

To avoid connectivity issues, we highly recommend:
* **Always testing your Cloud SQL Proxy configuration thoroughly** before adopting new Cloud SQL database versions or enabling advanced security features like Shared CA or Customer-managed CA.
* **Using the default Cloud SQL Proxy V2.**
* **Always testing your Cloud SQL Proxy configuration thoroughly** before adopting new Cloud SQL database versions or enabling advanced security features, especially if not using the default V2 proxy.

* The Dataproc team has updated the underlying Cloud SQL clients in Dataproc images to make use of Cloud SQL Proxy V2. The dataproc versions that are compatible with CloudSQL MySQL 8.4 are Dataproc versions 2.0.147, 2.1.96, 2.2.64 and 2.3.10 released on August 29, 2025. See [Dataproc release notes](https://cloud.google.com/dataproc/docs/release-notes) for any new updates.

Expand Down
28 changes: 19 additions & 9 deletions cloud-sql-proxy/cloud-sql-proxy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,6 +262,9 @@ readonly DB_ADMIN_PASSWORD

# Database password used to access metastore.
DB_HIVE_PASSWORD_URI="$(/usr/share/google/get_metadata_value attributes/db-hive-password-uri || echo '')"
DB_HIVE_METASTORE_REUSE="$(/usr/share/google/get_metadata_value attributes/db-hive-metastore-reuse || echo '')"
readonly DB_HIVE_METASTORE_REUSE

readonly DB_HIVE_PASSWORD_URI
if [[ -n "${DB_HIVE_PASSWORD_URI}" ]]; then
# Decrypt password
Expand Down Expand Up @@ -374,7 +377,6 @@ function get_metastore_instance() {
metastore_instance+="?port=${METASTORE_PROXY_PORT}"
fi
fi
metastore_instance="${metastore_instance//=tcp:/?port=}"
echo "${metastore_instance}"
}

Expand Down Expand Up @@ -522,18 +524,26 @@ function initialize_mysql_metastore_db() {

# Check if metastore is initialized.
if ! mysql -h 127.0.0.1 -P "${METASTORE_PROXY_PORT}" -u "${DB_HIVE_USER}" "${db_hive_password_param}" --get-server-public-key -e ''; then
mysql -h 127.0.0.1 -P "${METASTORE_PROXY_PORT}" -u "${DB_ADMIN_USER}" "${db_password_param}" --get-server-public-key -e \
"CREATE USER '${DB_HIVE_USER}' IDENTIFIED BY '${DB_HIVE_PASSWORD}';"
if [[ ! "${DB_HIVE_METASTORE_REUSE,,}" == "true" ]]; then
mysql -h 127.0.0.1 -P "${METASTORE_PROXY_PORT}" -u "${DB_ADMIN_USER}" "${db_password_param}" --get-server-public-key -e \
"CREATE USER '${DB_HIVE_USER}' IDENTIFIED BY '${DB_HIVE_PASSWORD}';"
else
log "Re-using exiting hive user account"
fi
fi

if ! mysql -h 127.0.0.1 -P "${METASTORE_PROXY_PORT}" -u "${DB_HIVE_USER}" "${db_hive_password_param}" --get-server-public-key -e "use ${METASTORE_DB}"; then
# Initialize a Hive metastore DB
mysql -h 127.0.0.1 -P "${METASTORE_PROXY_PORT}" -u "${DB_ADMIN_USER}" "${db_password_param}" --get-server-public-key -e \
"CREATE DATABASE ${METASTORE_DB};
GRANT ALL PRIVILEGES ON ${METASTORE_DB}.* TO '${DB_HIVE_USER}';"
/usr/lib/hive/bin/schematool -dbType mysql -initSchema ||
err 'Failed to set mysql schema.'
if [[ ! "${DB_HIVE_METASTORE_REUSE,,}" == "true" ]]; then
mysql -h 127.0.0.1 -P "${METASTORE_PROXY_PORT}" -u "${DB_ADMIN_USER}" "${db_password_param}" --get-server-public-key -e \
"CREATE DATABASE ${METASTORE_DB};
GRANT ALL PRIVILEGES ON ${METASTORE_DB}.* TO '${DB_HIVE_USER}';"
/usr/lib/hive/bin/schematool -dbType mysql -initSchema || err 'Failed to set mysql schema.'
log 'MYSQL DB initialized for Hive metastore'
else
log "Re-using exiting hive user account"
fi
fi
log 'MYSQL DB initialized for Hive metastore'
}

function initialize_postgres_metastore_db() {
Expand Down