One framework to🧑💻 Develop
data workflows with Python and SQL
Introduction to the VDK SDK
Get started with VDK SDK: ➡ Install Quickstart VDK. Only requirement is Python 3.7+.
|
VDK.SDK.2.mp4 |
Data Ingestion
Ingestion examples: ➡ Ingesting data from REST API into Database➡ Ingesting data from DB into Database ➡ Ingesting local CSV file into Database ➡ Incremental ingestion using Job Properties |
VDK.Ingestion.2.mp4 |
Data Transformation
Get started with transforming data: ➡ Data Modeling: Treating Data as a Product➡ Processing data using SQL and local database ➡ Processing data using Kimball warehousing templates |
Transform.VDK.2.mp4 |
Data Job Deployment (build, deploy, release)
VDK Control Service provides REST API for users to create, deploy, manage, and execute data jobs in a Kubernetes runtime environment.
Get started with deploying jobs in control service: ➡ Install Local Control Service with vdk server --install➡ Scheduling a Data Job for automatic execution ➡ Using VDK DAGs to orchestrate Data Jobs |
VDK.CS.2.mp4 |
Operations and Monitoring
Get started with operating and monitoring data jobs: ➡ Versatile Data Kit UI - Installation and Getting Started➡ VDK Operations User Interface - Versatile Data Kit |
VDK.UI.2.mp4 |
Lego like extensibility
Get started with using some VDK plugins: ➡ Browse available plugins➡ Interesting plugins to check out: Track Lineage of your jobs using vdk-lineage Import/Ingest or Export CSV files using vdk-csv ➡ Write your own plugin |
VDK.plugins.2.mp4 |
Support and Contributing
For Support, you can join our Slack channel, create an issue or pull request on GitHub to submit suggestions or changes.
If you are interested in contributing as a developer, visit the contributing page.
Contacts
- Message us on Slack:
☝️ Join the CNCF Slack workspace.
✌️ Join the #versatile-data-kit channel. - Join the next Community Meeting
- Follow us on Twitter.
- Subscribe to the Versatile Data Kit YouTube Channel.
- Join our development mailing list, used by developers and maintainers of VDK.
Code of Conduct
Everyone involved in working on the project's source code, or engaging in any issue trackers, Slack channels, and mailing lists is expected to be familiar with and follow the Code of Conduct.