How to recover deleted View in BigQuery? - google-bigquery

I have deleted a view in bigquery. I came to know there is an option to restore deleted tables based on table snapshot decorators. Is there any way to retrieve deleted bigquery views?

There is a way to get it back. You need to search for insertion logs rolled at a time of creating your view. This logs can be seen from stackdriver logging. Here are the steps :
Go to GCP console
Click on stackdriver logging
Click on arrow present in search text box and select "Convert to advance filter"
Now remove everything and paste below query in it. Don't forget to put your view name in a query.
resource.type="bigquery_resource"
protoPayload.methodName="tableservice.insert"
protoPayload.serviceData.tableInsertRequest.resource.tableName.tableId="Your_view_name"
You will get record of your view creation, Now click on Expand all and go to view section. There you can find a query used at a time of view creation.
Just paste that query in bigquery and click on save view.
Alternatively, if you want to search for updates to the view to recover a specific version you can use the following filter:
resource.type="bigquery_resource"
protoPayload.serviceData.tableUpdateRequest.resource.tableName.datasetId="<dataset_id>"
protoPayload.resourceName="projects/<project_id>/datasets/<dataset_id>/tables/<table_or_view_id>"
I hope this helps you get back your BQ view.

Related

Unexpected error Tracking number: c904462681469709

been trying to create a table in sandbox and i'm getting an "Unexpected error
Tracking number: c904462681469709". sometimes the table gets created, sometimes it doesn't.
any wizards that can help me with this?
cheers,
I ran into the same issue today, I do not know what causes the error, but I found that BigQuery has loaded my table. The steps I used are as follows:
Click the three dot drop down to create the table.
Fill out the source, destination, schema for the table.
After clicking 'create table' receive the error and close out the error window.
Close out of the create table window.
Refresh your BigQuery page.
Check the dataset you created the table under and it should be there.
I hope this method works for you as it did for me!
That happened to me too. So strange but yes I did the same thing Devin did. Took me forever trying to figure it out but it is what it is. Just refresh and keep going.

ALM Workflow - Script Editor - Update custom field on Refresh of Execution Grid

In HP ALM, using the Script Editor in Workflow, I created some code to count the number of fails for a selected test in the Test Execution grid. This calculation updates in the TestSetTests_MoveTo module. Not the most elegant solution since the user has to click every line to update, but it works.
My lead wants to have all of the values update on using the ALM Refresh button on the same page. I am looking through all of the different modules, but I don't see anywhere that I can add an update on refresh. Any ideas on how to accomplish this?
Thanks!
I figured out how to add functionality to the refresh button. I created a message box that showed the Action being performed when it was clicked. It's ExecutionGrid.RefeshAllExecGrid Then I added an if statement on ActionName to call my update code and it worked. Hopefully, this helps someone else.
**The misspelling is correct, unfortunately.

BigQuery Views cannot be edited, only deleted and re-saved

This is more of a bug report than a question, but Stack Overflow is the official support channel for BigQuery so I'm not sure where else to post this.
Right now if I have a view in BigQuery, when I try to edit it by clicking on "Details", editing the SQL, then clicking "Save View", I get the "View Saved" popup, but when I query the view again nothing has actually changed. The only way to change the view is to delete it and save a new one with the same name, which is pretty annoying every time I want to edit a view. This seems like a bug. Is it already known? Is there a timeline for it to be fixed? Is there somewhere else I should be reporting this? Thanks.
This is a UI-specific bug that we began pushing earlier in the week. The issue was exactly as your described: updating an existing view would report success, but not actually change the SQL query. We pushed a fix to production yesterday and the issue should now be resolved. You will need to refresh your BigQuery UI to pick up the new version and again be able to update views as expected.
Thanks for the bug report, and sorry for any inconvenience! Just FYI, another channel for bug reports (which Stack Overflow sometimes isn't a huge fan of) is our external issue tracker.

Creating a Connector - Query results refreshing in the same page

When creating a connector, in 'Recording a query', I follow two steps:
1-Accepted the User Agreement;
2-Executed a query.
The result is shown in the same page (without reloading), so import.io does not understand that the query has happened. Any workarounds?
Thanks a lot,
Renato
It sounds like when using the Connector, you are not inputing any text as a query. This is required for the Connector to finish recording.
One workaround you could do is hit the record button first. Then enter the URL of the webpage you wish to grab the data and push enter. Afterwards, click on Accepted the User Agreement. Lastly, Execute the query.

Reasons for Empty Dataset

Can you please explain the possible reasons that I'm unable to view the schema of a .csv dataset that I'm attempting to import (from a local file) into bq. The table name and icon appear in the left pane, but when I click on the table icon, I don't see a schema similar to the ones for the sample datasets. As far as I can tell, I'm correctly inputting the schema for each field name.
While the table is importing, it may show up in the left hand pane without a schema. If the import fails, then you'll never get a real table to be populated there. If you click on the job history link on the upper right side of the page, you should see your load job and you can see whether it succeeded or failed. If it failed, you should be able to click on it and see the errors from the job.