etl-ods-to-dwd

Manually trigger the QVL ETL pipeline from biz_ods to biz_dwd via direct SQL calls.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill etl-ods-to-dwd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: etl-ods-to-dwd
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-ops/skills/mj-etl-ods-to-dwd
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill etl-ods-to-dwd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill allows for the manual triggering of the QVL ETL pipeline, bypassing the standard 1-minute polling wait and quiet window, ensuring immediate data propagation from ODS to DWD.

Core Features & Use Cases

  • Immediate Data Sync: Trigger ETL when ODS data is ready and DWD results are needed instantly.
  • Cold Start Recovery: Refresh DWD tables that appear empty after a cold start or data loading.
  • Data Propagation Fix: Run ETL when data hasn't propagated as expected after insertion.
  • Use Case: After inserting new records into the biz_ods table, you need to see the results in the biz_dwd tables immediately for analysis. Instead of waiting for the scheduled cron job, you use this skill to force the ETL process.

Quick Start

Manually trigger the ETL process for ODS to DWD by saying "trigger ETL".

Frequently Asked Questions about etl-ods-to-dwd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually trigger an ETL pipeline from ODS to DWD in Postgres without waiting for scheduled polling?

To manually trigger an ETL pipeline from ODS to DWD, you can bypass the standard 1-minute polling wait and quiet windows by executing direct SQL calls. This forces immediate data propagation from the biz_ods to the biz_dwd tables.

Why does my DWD table show empty data after a cold start and how can I fix it?

DWD tables may appear empty after a cold start or data loading if the standard ETL polling hasn't executed yet. You can fix this by manually triggering the ETL process to force an immediate refresh and populate the biz_dwd tables.

What is the best way to force immediate data sync from biz_ods to biz_dwd tables for analysis?

The best way to force immediate data sync from biz_ods to biz_dwd tables is by manually triggering the ETL pipeline. This bypasses scheduled cron jobs and quiet windows, ensuring data is instantly available for analysis.

How does the ETL process handle write operations when using a read-only MCP connection versus direct Docker exec?

The ETL process handles write operations by using direct Docker exec commands, because standard read-only MCP connections cannot perform writes. It checks ODS ready signals first, then executes the write operations via Docker.

When should I manually trigger the ODS to DWD data propagation instead of relying on automated polling?

You should manually trigger ODS to DWD data propagation when immediate DWD results are required after ODS data insertion, or when automated data propagation fails and you need to bypass the quiet window for instant results.