Seems like a bug in a BigQuery join

[marcromeyn]

Bug

Joins don't work for me with BigQuery as database, seems a problem with the way Metabase aliases fields and tables.

• Your browser and the version: Chrome 52.1
• Your operating system: OS X 10.12
• Your databases: BigQuery
• Metabase version: 0.21.1
• Metabase hosting environment: AppEngine
• Metabase internal database: MySQL

Repeatable steps to reproduce the issue

The error is as follows:
Field 'logs.table_conversations__via__conv.agent_id' not found on either side of the JOIN

The SQL-query Metabase creates is:

SELECT
  [logs.table_conversations__via__conv.agent_id] AS [logs.table_conversations__via__conv.agent_id]
FROM
  [logs.table_chatuser_events]
LEFT JOIN
  [logs.table_conversations] [table_conversations__via__conv]
ON
  [logs.table_chatuser_events.conversation_id] = [table_conversations__via__conv.id]
GROUP BY
  [logs.table_conversations__via__conv.agent_id]
ORDER BY
  [logs.table_conversations__via__conv.agent_id] ASC
LIMIT
  2000

It should be this (add the dataset to table you join with):

SELECT
  [logs.table_conversations__via__conv.created_by] AS [logs.table_conversations__via__conv.created_by]
FROM
  [logs.table_chatuser_events]
LEFT JOIN
  [logs.table_conversations] [logs.table_conversations__via__conv]
ON
  [logs.table_chatuser_events.conversation_id] = [logs.table_conversations__via__conv.id]
GROUP BY
  [logs.table_conversations__via__conv.created_by]
ORDER BY
  [logs.table_conversations__via__conv.created_by] ASC
LIMIT
  2000

Should be a very straightforward fix.

[asafeilam]

I also experienced the same problem.
what to do?

[MiBaDK]

Hi guys, any plans for this one?

[MiBaDK]

Having dreams about one day waking up and seeing a patch for this one or at least assigned a milestone. That would be a great day :)

[MiBaDK]

https://www.bountysource.com/issues/41273748-seems-like-a-bug-in-a-bigquery-join

Anyone up for joining?

[MiBaDK]

Hi, a proposed fix has been committed some time ago. Any chance of getting this in a release soon :)

[vcGomez]

I also would like to know about this issue :)

[vbronsky]

Any news about this issue with BQ joins in custom question? Any chance to add this fix to release?

I'm still have an error:

Field 'METABASE_DATA.SKU__via__SKU_code.Trade_group_in_price_model' not found on either side of the JOIN