Assigned
Status Update
No update yet.
Comments
va...@google.com
sa...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
The customer is unable to create search indexes within a named schema in Spanner. Based on public documentation, search indexes are supported in Spanner, but only within the default schema. When attempting to create a search index on a table in a named schema, the following error is encountered:
"Search index not yet supported in the named schema”
Business Impact:
The lack of support for search indexes in named schemas is a showstopper for the customer, preventing them from moving beyond the Proof of Concept (PoC) stage. Their application architecture requires named schemas for multi-tenancy and logical data separation, and without search index support, they are unable to proceed with development.
Workarounds & Research:
No official workarounds exist to enable search indexes in named schemas and there is no official documentation explicitly stating this limitation.
Request:
Feature Addition: Enable support for creating search indexes in named schemas in Spanner.
Documentation Update: If the feature is not planned, update public documentation to clearly state that search indexes are limited to the default schema.