Let’s further enhance our pipeline and make it even more agile! Not the most effective approach.īut what if we could provide all OData services upfront in an external datastore? That’s the plan for today. If we want to extract data from many services, we have to start the pipeline multiple times, each time providing the OData service name, entity and host. The extraction job can only extract a single OData service at a time, and we still have to provide parameter values manually. It was a great improvement, but the process still has two main disadvantages. It allows us to change the OData service we want to use without modifying the pipeline or resources. Then, a week later, we enhanced the design to support parameters, which eliminated some of the hardcoded values. In the first episode, we’ve built a simple pipeline that extracts data from a selected OData service and saves it to the data lake. Welcome to the third episode of this mini blog series, where I show you how to deal with OData extraction from the SAP system using Synapse Pipelines. Before implementing data extraction from SAP systems please always verify your licensing agreement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |