One Request Per Batch Functionality for Web Client Stages

The option is there to have one request per batch in the stage, but nothing is populating the request body.

The current workaround is to aggregate the records from the batch into a single record using the following Groovy script and configuring the Web Client stage to have one record per request:

whole_data = ""
records = sdc.records
for (record in records) {
    try {
      whole_data = record.value['json'] + "," + whole_data
      //for_debugging sdc.log.info("whole_data = " + whole_data)
    } catch (e) {
        // Write a record to the error pipeline
        sdc.log.error(e.toString(), e)
        sdc.error.write(record, e.toString())
    }
  
}
//for_debugging sdc.log.info("(outside loop) whole_data = " + whole_data)
newRecord = sdc.createRecord("consolidated record")
newRecord.value = sdc.createMap(false)
t_whole_data = whole_data.dropRight(1)//drops trailing comma
t_whole_data = "[" + t_whole_data + "]"//adds array brackets
//for_debugging sdc.log.info("(outside loop) t_whole_data = " + t_whole_data)
newRecord.value['json2'] = t_whole_data
sdc.output.write(newRecord)

We would then pass this in the request body as ${record:value('/json2')}.

The one request per batch feature does work and automatically aggregates the records in the HTTP Client stages.

Needed By

Yesterday (Let's go already!)

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

One Request Per Batch Functionality for Web Client Stages