-
Notifications
You must be signed in to change notification settings - Fork 77
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
Default Looker Model or Explore is blank or unspecified #105
Comments
hey @LydiaB123 can you share your .env file ? |
Hi @antfido, here is my .env file
|
and do you remember to update your bundle.js file after changing .env file ? and did you check all of the steps from troubleshooting steps ? |
Yes, I did update my
Looking into it I'm wondering if it is due to the explore and model I reference in my EDIT: I have moved the data into the same Google CLoud Project so it could use the same connection and I still get the same error. |
With the new version, you dont need to specify looker model and explore in .env file. Based on entries in samples table, you will the dropdown on the extension to select the explore. Please make sure to load below tables if you are using BQ |
I have the exact same error, these 3 tables were properly populated with model_name[] format in the BQ table |
Hi all, I'm getting the exact same error as @LydiaB123 with a newly forked version. Does anyone have any update? |
Default Looker Model or Explore is blank or unspecified
Error Name:
Error Message:
Default Looker Model or Explore is blank or unspecified
Diagnosis:
The error is likely related to your Look specific .env variables.
Troubleshooting Steps
Check the LOOKML_MODEL & LOOKML_EXPLORE env variables for your extension. Are they valid (spelling) & exist in your Looker instance?
Make sure your user has access to this model and explore. At the very least with see_lookml permissions.
Check the Connection environment variables. Do valid BQ connections by those names exist in your Looker instance?
.env file
VERTEX_BIGQUERY_LOOKER_CONNECTION_NAME=explore_assistant
VERTEX_BIGQUERY_MODEL_ID=.explore_assistant.explore_assistant_llm
BIGQUERY_EXAMPLE_PROMPTS_CONNECTION_NAME=explore_assistant
BIGQUERY_EXAMPLE_PROMPTS_DATASET_NAME=.explore_assistant
LOOKER_MODEL=<model_name of the explore that I want the explore assistant to use - not the model the explore assistant is using>
LOOKER_EXPLORE=<explore_name of the explore that I want the explore assistant to use>
I would appreciate any suggestions you may have on how to investigate and troubleshoot this issue.
The text was updated successfully, but these errors were encountered: