메뉴
Registers cds-data-pipeline event hooks on DataPipelineService. Use when customizing PIPELINE.READ, PIPELINE.MAP, PIPELINE.WRITE, filtering records, or extending pipeline behavior without forking the engine.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pipeline-hooks |
| description | Registers cds-data-pipeline event hooks on DataPipelineService. Use when customizing PIPELINE.READ, PIPELINE.MAP, PIPELINE.WRITE, filtering records, or extending pipeline behavior without forking the engine. |
PIPELINE.START → PIPELINE.READ → (PIPELINE.MAP → PIPELINE.WRITE)* → PIPELINE.DONE
Aliases: PIPELINE.MAP / PIPELINE.WRITE for batch handlers.
Use CAP's standard handler API scoped by pipeline name:
const pipelines = await cds.connect.to('data-pipeline');
pipelines.before('PIPELINE.MAP', 'LocalProducts', async (req) => {
req.data.sourceRecords = req.data.sourceRecords.filter(r => r.active);
});
pipelines.after('PIPELINE.DONE', 'LocalProducts', async (req) => {
// post-run notification, cache invalidation, etc.
});
Pipeline name matches addPipeline({ name: '...' }) or the federated entity name for @federation.replicate bindings.
When using @federation.replicate, consumers do not call addPipeline directly, but hooks still work:
pipelines.before('PIPELINE.MAP', 'ReplicatedProducts', async (req) => {
req.data.sourceRecords = req.data.sourceRecords.filter(r => !r.blocked);
});
❌ Wrong — parallel custom hook system outside DataPipelineService.
✅ Correct — before / on / after on PIPELINE.* events.
❌ Wrong — synchronous outbox for CUD-like side effects that break request/response contracts in delegate flows.
✅ Correct — hooks for in-process MAP/WRITE transforms; use outbox only for fire-and-forget notifications.
❌ Wrong — SELECT-then-INSERT/UPDATE in custom WRITE handlers.
✅ Correct — use UPSERT patterns the engine provides; transform in MAP.
Creates @federation.replicate consumption views for scheduled remote-to-local sync in SAP CAP. Use when copying remote OData or REST data locally, configuring schedule, delta sync, or the replicated aspect.
Registers cds-data-pipeline jobs via addPipeline with correct source and target shapes. Use when creating replicate, materialize, or move-to-service pipelines, configuring delta sync, schedules, or REST/OData sources.
Enables the cds-data-pipeline Pipeline Console UI for the /pipeline management API. Use when adding pipeline monitoring, running pipelines manually, viewing run history, inspecting source/target data, or scaffolding with cds add pipeline-console.
Installs and configures cds-data-pipeline in a SAP CAP project. Use when adding the pipeline plugin, importing tracker schema, exposing the management OData service, or connecting to the pipeline engine.
Handles cross-service $expand and navigation in cds-data-federation. Use when expanding local to remote, remote to local, cross-provider mashups, navigation filters, or association renames across federated entities.
Creates @federation.delegate consumption views on remote OData entities in SAP CAP. Use when proxying remote data, adding field renames, association renames, read-only defaults, CUD opt-in, or delegate caching.