POST /v1/op/data/startExtractAndLoad request body definition is invalid

APIs & Connectors
1

Hello Visier Developer community,

after testing the latest version of the data-in-apis.yaml (available here) OAS3 spec, we found out that the request body definition for the POST /v1/op/data/startExtractAndLoad` is invalid. If we call the endpoint with a request body as specified in the OAS3 spec:

{
	"model": {
		"allTenants": false,
		"tenants": [
			"<VALID_TENANT>"
		],
		"connectorIds": [
			"<VALID_CONNECTOR_IDS>"
		],
		"dataCategoryId": "<VALID_DATA_CATEGORY_ID>",
		"runProcessingJob": true,
		"disableArtifactGeneration": false,
		"publishDataLoadArtifacts": true,
		"batchSizeOverride": 0,
		"sqlBatchSize": 10000,
		"forceUpdateExistingArtifacts": true
	}
}

we get the following error:

{
	"localizedMessage": "Bad request: rci=DP810005 Cannot find field: model in message visier.admin.jobs.ExtractDataAndLoadDTO",
	"message": "",
	"rci": "RCIY3003012",
	"code": "VSE_BADREQUEST",
	"userError": true
}

The contents of the StartExtractionModel object definition shouldn’t be placed under the model parameter of the StartExtractionRequest object definition. Could you please the fix the OAS3 spec so we don’t have to do manual updates? Furthermore, the description of the StartExtractionModel is not correct.

Thanks in advance,
Bogdan

2

Thank you Bogdan for the report. We will take a look right away.

Thanks,

Vincent