Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

primary key issues #1

Open
iooab100 opened this issue Jan 19, 2022 · 0 comments
Open

primary key issues #1

iooab100 opened this issue Jan 19, 2022 · 0 comments

Comments

@iooab100
Copy link

input_data view, the instructions are to change your primary key and the example was given like this.

dimension: ga_session_id {
type: string
primary_key: yes
sql:
${TABLE}.ga_session_id ;;
}

However, when I defined my primary key, I received multiple primary key errors in Looker Explore.

So, I had to do this to prevent that error, in my input_data....

dimension: id {
primary_key: no
type: string
sql: ${TABLE}.id ;;
}

this is my primary key

dimension: transaction_id {
type: number
primary_key: yes
sql: ${TABLE}.TransactionID ;;
}

I'm not receiving predictions. Any chance there is an issue with my primary key being a number and the join parameter defined in step 1.

join: automl_predict {
type:full_outer
relationship: one_to_one
sql_on: ${input_data.transaction_id} = ${automl_predict.input_data_primary_key} ;;
}

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

No branches or pull requests

1 participant