Status Update
No update yet.
Comments
va...@google.com
su...@gmail.com
su...@gmail.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.
su...@gmail.com
Yt
ro...@google.com
su...@google.com
Hello,
Thank you for reaching out to us with your request.
I have forwarded your request to the Engineering team.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
di...@google.com
For the 2nd question about sequence: Technically, you can use a sequence for multiple columns, but keep in mind that you are retrieving bit-reversed positive values from a shared object. This means that in this shared sequence, you're churning through the positive int64 spaces more quickly, and the sequence has to serve many more requests for values from all columns. While we don't find any bottleneck from our end, you should benchmark the setup with your actual write load to identify any potential issues.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
I am working with a customer on migrating there current cloudSQL database to spanner. and currently we are facing issues and need clarification for below two queries:
1. Customer has some approx 50 indexes and some sequences in there environment distributed across 30 tables. We are using alembic migrations to migrate the database schema from there existing cloud SQL to spanner database. initially the index and sequence creation is quick but last 7-8 indexes and sequences are getting created very slowly even when table is completely freshly created and does not have any data. you can see the start and end time of index creation operation in screenshot attached with ticket.
2. customer do not want to manage multiple Sequences in there database hence they want to create only one sequence and use that same sequence for all the columns where they need integer unique keys. We need to know if this can cause some bottlenecks or can cause some performance issues for spanner later on. Also what's the limit for these sequences.