Hi! We are trying to ingest our lookml from our gi...
# ingestion
s
Hi! We are trying to ingest our lookml from our github repository. Im doing a POC but runnig into issues:
Copy code
Source (lookml) report:
{'workunits_produced': 0,
 'workunit_ids': [],
 'warnings': {},
 'failures': {'/models/google_ads.model.lkml': ['cannot resolve include /views/vm_datawarehouse/sales/sales_orderline.view.lkml']},
 'models_discovered': 9,
 'models_dropped': [...],
 'views_discovered': 0,
 'views_dropped': []}
Sink (datahub-rest) report:
{'records_written': 0,
 'warnings': [],
 'failures': [],
 'downstream_start_time': None,
 'downstream_end_time': None,
 'downstream_total_latency_in_seconds': None}

Pipeline finished with failures
Note that im running this in docker:
Copy code
FROM python:3.8-slim-bullseye

WORKDIR /app

COPY ./models /models
COPY ./views /views
COPY ./receipt.yml /app/

RUN pip install acryl-datahub[lookml]

RUN ls /views/vm_datawarehouse/sales/
CMD ["datahub", "ingest", "-c", "receipt.yml"]
With the receipt:
Copy code
source:
  type: "lookml"
  config:
    # Coordinates
    base_folder: /models/

    # Options
    api:
      # Coordinates for your looker instance
      base_url: <https://host>

      client_id: ID
      client_secret: SECRET

    github_info:
      repo: VanMoof/looker
    model_pattern:
      allow:
        - "google_ads"

sink:
  type: "datahub-rest"
  config:
    server: "<http://HOST:8080>"
    token: "TOKEN"
Note that when running the 'ls' I can see the view in the correct folder. Any ideas why this is failing? Something particular related to the absolute paths?
I have been way too quick asking this question. Going back to the docs, it says the config.base_folder should contain the folder with the models and the looks. I pointed to the folder only containing the models. After correcting this it works as expected 🙂
l
Hi @shy-island-99768! Glad you were able to get it working 🙂 Gentle reminder to please post large blocks of code/log output in threads; it’s a big help for us to keep track of which questions are sill unanswered across all of our support channels teamwork