Another Looker/LookML bug we've spotted: we are a...
# ingestion
p
Another Looker/LookML bug we've spotted: we are also finding examples of Charts that don't have lineage to their explores Interestingly our staging environment has the correct lineage (and is running a much older version of the looker/lookml ingestors) Can see them in the properties field, but no lineage is actually being established to these explores
g
Hey @plain-farmer-27314 would you be able to share the query that populated the chart / more information on the explore? My guess is something w/ the setup of this chart is hard for us to parse.
p
I can - but based on the image it looks like the explore's fields were correctly parsed, they just weren't sent as lineage events
The explore itself also has correct lineage to the view and further, so its just the chart <-> explore connection that's missing
Bump - what's the best way I can provide info on the above chart?
g
Hey @plain-farmer-27314 - is that screenshot you shared w/ the
upstream_fields
from your chart entity?
but you’re saying that chart has 0 upstream entities?
also cc @dazzling-judge-80093 - any thoughts on what could be the issue here?
d
I think with the query we can make sure it is not related to the sql parser or actually you can switch to the old query parser with :
sql_parser: datahub.utilities.sql_parser.MetadataSQLSQLParser
p
I will say I have a staging environment that's running an older version of the looker ingest, and the lineage was parsed correctly
@green-football-43791 correct, the screenshot contains the upsteam_fields from the chart entity, and yet it has 0 upstream entities
Gonna run with older version of the SQLParser
@dazzling-judge-80093 is that config in the looker or lookml ingest? i don't see it here: https://datahubproject.io/docs/metadata-ingestion/source_docs/looker
d