Google Data Studio

本文介绍了Google Data Studio-MySQL的Cloud SQL连接器错误的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我已经在GCP上创建了一个MySQL 8.0实例，并试图通过它连接 Google Data Studio提供了适用于MySQL的Cloud SQL连接器. 我已按照 support中提供的所有说明进行操作. google/datastudio/answer/7020436?hl=zh-CN&ref_topic=6370347 我可以通过MySQL Workbench以及使用SSL(服务器证书，客户端证书和客户端密钥)的sql命令连接到MySQL，但无法通过"MySQL的Cloud SQL"连接. . 我什至无法通过我的SQL连接器"建立连接.

我已经打开了公共IP，甚至将所有Google数据工作室IP列入了白名单，而"MySQL连接器的Cloud SQL"并不需要这些IP.

我尝试使用root用户以及新用户"testuser"可以访问％"

请让我知道可能出什么问题了吗?我应该研究IAM的任何限制吗?

更新-如果gcp cloud MySQL版本为5.7，则用于MySQL的Cloud SQL"会显示为连接器成功建立连接.看来问题出在连接到Cloud MySQL8.0时

解决方案

您的配置没有错.这是因为Datastudio还不支持连接到MySQL版本8.这是一个支持线程，其中包含一种解决方法，它使用ProxySQL. /p>

另一种替代方法是为MySQL实例创建另一个Cloud SQL，并使用5.7版.

此外，这是Google提供的公共问题跟踪器，您可以在其中接收更新.只需发表评论并指出您已受到该问题的影响.

请注意，该功能推出时没有ETA.

I have created a MySQL 8.0 instance on GCP and trying to connect to it through Cloud SQL for MySQL connector available with Google data Studio . I have followed all the instructions provided in support.google/datastudio/answer/7020436?hl=en&ref_topic=6370347 I could connect to the MySQL through MySQL Workbench and as well as through my sql command using the SSL (server cert ,client cert and client key) but not able to connect through "Cloud SQL for MySQL connector" . I am not able establish connection through even "My SQL connector".

I have opened Public IP and even whitelisted all the google data studio IPs which is not needed for "Cloud SQL for MySQL connector"

I tried using the root user as well as the new user "testuser" with access from '%'

Could you please let me know what could be wrong? are there any IAM restrictions should I look into?

UPDATE - If the gcp cloud MySQL version is 5.7 , the "Cloud SQL for MySQL" connector successfully establishes the connection. It looks like the issue is while connecting to Cloud MySQL8.0

解决方案

There's nothing wrong with your configuration. It's that Datastudio doesn't support connecting to MySQL version 8 yet. Here's a support thread that contains a workaround, it uses ProxySQL.

Another alternative is that you create another Cloud SQL for MySQL instance and use version 5.7.

Also, here's a public issue tracker from Google where you can receive an update. Simply leave a comment and indicate that you're affected by the issue.

Take note that there's no ETA when the feature will roll out.