+1I’ve got a customer where we load 550+ tables into the ODX (ADLS Gen2). The data source is Dedicated Pool, and because of intermittent errors in Azure, a few tables fail every day. I use the On Demand feature in v21 in combination with retries in traditional TX packages to minimize the number of fails.
It would be nice if we could use Exmon’s Orchestration platform to handle retries of ODX transfers at table level.
+5Hey
+1Hey
What I’m after is retries at the v21 ODX transfer level, i.e. without packaging the ODX transfer into an on-demand MDW transfer (if that makes sense). We currently don’t have retries at source table level in ODX transfer tasks, only in MDW packages … and I have a use case where we want to separate the ODX transfer from the MDW transfer with retries at ODX level.
I just wondered if Orchestration could ‘unpack’ an ODX transfer task and add retries at table level.
I understand this would require integration of Orchestration and our cloud repository … maybe it’s better/easier to simply add retry-functionality to ODX transfer tasks?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
