Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add 'jobs' to the meltano project json schema
See original GitHub issueThe jobs key currently shows an error in meltano.yaml. This is because it is missing in the schema definition.
Issue Analytics
- State:
- Created a year ago
- Comments:25 (12 by maintainers)
Top Results From Across the Web
Complete Tutorial - Meltano Documentation
The first plugin you'll want to add is an extractor, which will be responsible for pulling data out of your data source. To...
Read more >Draft: Resolve "Create a JSON schema for `meltano.yml` and ...
Add a CHANGELOG.md entry in the Unreleased section. Once your merge request is complete, please assign it a Meltano maintainer for review ...
Read more >tap-spreadsheets-anywhere/README.md at master - GitHub
The Meltano configuration for this tap must contain the key 'tables' which ... you can hardcode the json schema datatype to override //...
Read more >My Journey Towards Getting Started With Meltano - Medium
After all, we demonstrate how to prevent inconsistent schema between the source ... Added extractor 'tap-bigquery' to your Meltano project
Read more >meltano - PyPI
The gitlab-runner project contains a meltano.yml file: ... Data science; add more machine learning (ML) and Artificial Intelligence (AI) ...
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 Free
Top 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
@pnadolny13 i don’t think it’s just feature drift related, quite a few of the top-level keys (transformers, orchestrators, etc) in the discovery jsonschema are also failing because of mismatches in required fields (i.e. getting passed an unexpected
variantkey or missing alogo_urlkey).@vicradon have a peek at the Contributor Guide, particularly the prereq’s section: https://docs.meltano.com/contribute/prerequisites
That guide can help get you setup with a local dev setup and a locally built meltano. With that in place, you’ll also be able to run validation on your schema entries by running a:
@pnadolny13 might have some other tips/tricks but a local dev setup + validate_json_schema.py are the two pieces that’ll help the most I think.