Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supabase Self-hosted: Getting Api Gateway logs in BigQuery failes with error 'Name metadata not found inside t at' #2245

Open
srasul opened this issue Nov 4, 2024 · 0 comments

Comments

@srasul
Copy link

srasul commented Nov 4, 2024

We are using Supabase Self-hosted with BigQuery as the 'sink' for our logs. When trying to fetch the logs in Supabase Studio, we get the following error:

{
  "code": 400,
  "errors": [
    {
      "domain": "global",
      "location": "q",
      "locationType": "parameter",
      "message": "Name metadata not found inside t at [1:1060]",
      "reason": "invalidQuery"
    }
  ],
  "message": "Name metadata not found inside t at [1:1060]",
  "status": "INVALID_ARGUMENT"
}

Analyzing the query that is sent to BQ, we see that in the query we are selecting t.metadata from tables.

image

But when I look at the data in some of the tables, I notice we have no data in these tables, so the only columns in the tables are:

  • timestamp
  • id
  • event_message

So therefore, we are trying to query for a column that does not exist. And it see that even though this big-query SQL has the SQL to query for all the tables, only one table is actually queried. But since we send the SQL for all tables, this means that the SQL has to be valid for all the tables.

image

Can you advise how we can proceed with this? or steps we can take to get these queries in BQ to run without any errors?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant