Skip to content
Discussion options

You must be logged in to vote

There's no ODI connector as of 2.0.7 (the latest release). I checked the pipeline service types and the ingestion sources at that tag, and main and 2.1.0-rc1 don't add one either. So yes, it's custom work, but what you've built from the Package/Mapping XML is the right foundation. Two ways to run it:

  1. Custom connector. Wrap your parser in a class extending metadata.ingestion.api.steps.Source whose _iter yields CreatePipelineRequests, then AddLineageRequests. The default metadata-rest sink writes both. There's a working pipeline example. Package it, install it into your ingestion image, and add a Pipeline service of type Custom with sourcePythonClass set to your class (docs). You then get…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by monkeymagik
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants