Adding Project ID to Project-Number-only project breaks BQ web console

[GoogleCodeExporter]

Could be related to 
https://code.google.com/p/google-bigquery/issues/detail?id=68 though that issue 
doesn't describe my problem.

What steps will reproduce the problem?
1.Create a project with only a project number
2.Start using BQ console and create some datasets / tables
3.Add a Project ID to your project

What is the expected output? What do you see instead?

My project's datasets should still be listed in the top section of the sidebar. 
 Instead that section says "No datasets found in this project."

Adding the project via the 'Switch to Project -> Display Project' menu shows 
the datasets among the other external project datasets, but prefixed with the 
Project Number.  The top section still contains the message "No datasets found 
in this project."

What version of the product are you using? On what operating system?

Maybe https://bigquery.cloud.google.com/js/3933530382-bigquery.js ?
Chrome 37 on OSX
Please provide any additional information below.

Original issue reported on code.google.com by dj...@reverbnation.com on 24 Sep 2014 at 8:27

[GoogleCodeExporter]

Unfortunately our web UI gets a little confused when you assign a project ID to 
a project. The API returns inconsistent values in the projectId field for a 
little while, and the UI doesn't know which data to associate with which 
project.

Rest assured your data is still there, and the problem will be smoothed out 
within 24 hours when a background task cleans up the metadata. You should still 
be able to run queries, and the command line tool should still work.

Original comment by jcon...@google.com on 24 Sep 2014 at 8:38

[GoogleCodeExporter]

Hmm, I don't think that is what is happening here.  Could it be because the 
project ID was created with a : in it (It was created through the cloud SQL UI)?

Also, another bit of unexpected behavior, I can't save results to tables in the 
pre-Project-ID datasets.  When I select the project they belong to, they don't 
show up as options in the dataset select.

Original comment by dj...@reverbnation.com on 29 Sep 2014 at 6:22

[GoogleCodeExporter]

Hmm, why don't you think that's the issue? Is it because it has continued for 
more than 24 hours? If so, it could be that there's an issue with the metadata 
groomer task that usually cleans up these problems. (The symptoms you've 
described are still very consistent with the previous diagnosis.)

What's your project ID? It's okay to have a ':' in it as long as that's the 
separator for a domain (e.g., "google.com:myproject"), but the project ID 
itself shouldn't have a ':' in it. If you'd prefer not to post your project ID 
here, you can send mail to jcondit@google.com.

The save-to-tables issue might be caused because the newly-created tables have 
the newly-assigned project ID, but the dataset still has the old project 
number, and the UI doesn't know which dataset to associate the table with. 
Hopefully you should be able to save to a newly-created dataset, and you should 
be able to see the tables saved in the old dataset with the command line tool.

Original comment by jcon...@google.com on 29 Sep 2014 at 11:13

[GoogleCodeExporter]

Please follow up if you're still seeing issues!

Original comment by jcon...@google.com on 23 Jun 2015 at 4:31

• Changed state: Done