Cloud Spanner报错：Cannot read properties of null (reading 'join') 问题排查求助

Hey there, let's work through this issue together. Even though you deleted the StudentView you created, the error persisting suggests this might be a frontend caching issue, metadata sync delay, or a temporary Cloud Console glitch. Here's what you can try step by step:

1. Verify Student Table Data Exists Outside the Cloud Console #

First, rule out whether the problem is with the table itself or just the Cloud Console frontend:

• Use the gcloud CLI to run a query directly against your Spanner database:

  gcloud spanner databases execute-sql YOUR_DATABASE_NAME \
    --instance=YOUR_INSTANCE_NAME \
    --sql="SELECT * FROM Student LIMIT 10;"
  

• If this returns your expected data, the issue is definitely with the Cloud Console interface, not the table or data itself.

2. Clear Cloud Console Cache & Use Incognito Mode #

Cloud Console can sometimes cache outdated metadata (like references to your deleted view) which causes this kind of frontend error:

• Clear your browser's cache and cookies for console.cloud.google.com
• Open a new incognito/private browsing window and navigate back to your Spanner database
• Try viewing the Student table again

3. Refresh Database Metadata in Cloud Console #

Sometimes manually refreshing the database view can resolve lingering metadata issues:

• In the Cloud Console, navigate to your Spanner database's overview page
• Click the Refresh button (usually a circular arrow icon) at the top of the page
• Wait a few seconds, then navigate back to the Student table

4. Check for Metadata Sync Delays #

Spanner is a distributed system, and metadata changes (like deleting a view) can take a few moments to propagate fully:

• Wait 5-10 minutes after deleting the view, then try accessing the Student table again
• If you recreated the view earlier, delete it again and give it more time to sync before checking

5. Reach Out to Google Cloud Support (If All Else Fails) #

If none of the above steps work, this might be a rare backend metadata issue that requires Google's support team to investigate:

• Provide them with your Spanner instance name, database name, the exact error message, and a timestamp of when the issue started
• They can check for any underlying metadata inconsistencies tied to your Student table

内容的提问来源于stack exchange，提问作者Stinkybadger