Column Type None Error - Field's Not Converting To Dimensions
See original GitHub issueWhen running dbt2looker --tag marts
on my mart models, I receive dozens of errors around none type conversions.
20:54:28 WARNING Column type None not supported for conversion from snowflake to looker. No dimension will be created.
Here is the example of the schema.yml
file.
The interesting thing is that it correctly recognizes the doc that corresponds to the model. The explore within the model
file is correct and has the correct documentation.
Not sure if I can be of any more help but let me know if there is anything!
Issue Analytics
- State:
- Created 2 years ago
- Comments:19
Top Results From Across the Web
cant fix Error converting data type varchar to numeric.
Error converting data type varchar to numeric. runs fine for below:: Select *from ABC WHERE Phone ='50012765428'. there are no index, keys, ...
Read more >pyspark: ValueError: Some of types cannot be determined ...
In order to infer the field type, PySpark looks at the non-none records in each field. If a field only has None records,...
Read more >Error : Cannot convert value " of type Text to type Integer
Error : Cannot convert value " of type Text to type Integer · Select the column with a left click · In the...
Read more >Data Types - Tableau Help
Sometimes Tableau incorrectly interprets the data type of a field. For example, Tableau ... Dates and text values are dimensions, and numbers are...
Read more >Data Studio Tip: Convert Dimensions to Metrics | Mixed Analytics
To address this, open the drop-down menu and select an aggregate function for your number. This aggregate function can be 'None', meaning it ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nevermind, I see the comment in the code. With that, I think this is a resolved issue!
That seemed to do the trick! I noticed that
TIMESTAMP_TZ
seems to be producing an error. This is helpful in pointing out columns that I need to convert toTIMESTAMP_NTZ
but figured I’d flag.