Assigned
Status Update
Comments
th...@extendaretail.com <th...@extendaretail.com> #2
Forgot to add screenshots.
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com> #3
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
1. Spanner Studio yields faulty results when selecting. In short, the problem is visible when running the following query (details in steps to reproduce), the result is 3501 records counted:
WITH test AS (
SELECT d.* from config_data d
WHERE
d.tenant_id = 'CIR7nQwtS0rA6t0S6ejd'
)
select count(*) from test
2. While running the following yields between (this is strange and seems random) 322 - 345 records:
SELECT d.* from config_data d
WHERE
d.tenant_id = 'CIR7nQwtS0rA6t0S6ejd'
What you expected to happen:
1. I expect the same query (problem #2) will result in the same dataset as long as the data has not been altered
2. I expect the same amount of records to be returned. With or without a CTE. Problem #1
Steps to reproduce:
1. Load the schema and data into spanner
2. Run the queries in Spanner Studio.
Comparing the Spanner Studio results against `compare.mjs` should make the issue clear.
Other information (workarounds you have tried, documentation consulted, etc):
This is only reproducible in Spanner Studio. Using the NodeJS SDK we do not see this problem.
❯ nvm current
v22.13.1