Deploying Spanner schema changes with liquibase results in INVALID_ARGUMENT: io.grpc.StatusRuntimeException Unsupported concurrency mode

[jarchana]

Deploying Spanner changes using liquibase results in the error: Unsupported concurrency mode in query using INFORMATION_SCHEMA..

Using liquibase version : 4.25

Full error:

Iliquibase.exception.DatabaseException:
com.google.cloud.spanner.jdbc.JdbcSqlExceptionFactory$JdbcSqlExceptionImpl: 
INVALID_ARGUMENT: io.grpc.StatusRuntimeException: 
INVALID_ARGUMENT: Unsupported concurrency mode in query using INFORMATION_SCHEMA. 
- Statement: 'SELECT TABLE_CATALOG AS TABLE_CAT, TABLE_SCHEMA AS TABLE_SCHEM, TABLE_NAME,\n
       CASE WHEN TABLE_TYPE = 'BASE TABLE' THEN 'TABLE' ELSE TABLE_TYPE END AS TABLE_TYPE,\n
       NULL AS REMARKS, NULL AS TYPE_CAT, NULL AS TYPE_SCHEM, NULL AS TYPE_NAME,\n
       NULL AS SELF_REFERENCING_COL_NAME, NULL AS REF_GENERATION\n
FROM INFORMATION_SCHEMA.TABLES AS T\n
WHERE UPPER(TABLE_CATALOG) LIKE @p1\n
  AND UPPER(TABLE_SCHEMA) LIKE @p2\n
  AND UPPER(TABLE_NAME) LIKE @p3\n
  AND (\n
            (CASE WHEN TABLE_TYPE = 'BASE TABLE' THEN 'TABLE' ELSE TABLE_TYPE END) LIKE @p4\n
        OR\n
            (CASE WHEN TABLE_TYPE = 'BASE TABLE' THEN 'TABLE' ELSE TABLE_TYPE END) LIKE @p5\n
    )\n
ORDER BY TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME'\n
     at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:98)
     at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData.getTables(JdbcDatabaseSnapshot.java:1135)

[admah]

@jarchana here is a related Stack Overflow with a few possible solutions: Connecting Google Cloud Spanner with Liquibase - Stack Overflow

Do any of those solutions help with the issue?

[jarchana]

from the shared link, one proposed solution is -
by setting the appropriate mode through code:

1. Switch to autocommit: SET AUTOCOMMIT=TRUE
2. Switch to read-only: SET READ ONLY=TRUE

should i turn this setting on spanner database?

[jarchana]