...
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Is the requestId in the southbound request equal to the dataJobId coming in from the northound interfaces? (see writeJob for example) | Can the dataJobId used as the requestId? Csaba Kocsis |
Csaba Kocsis and Toine Siebelink agreed that requestId should be renamed to jobId on all interfaces |
NCMP → DMI
As part of the overall datajob solution there must be an interface for data flow between the NCMP-lib in DCM and the DMI Plugin.
...
Method: GET
Path: /dmi/v1/dataJobdataProducer/{requestIddataProducerd}/dataProducerJob/{dataProducerJobIddataProducerdJobId}/result?dataProducer={dataProducerId}&destination={destination}
...
| Name | Description | Location | Type | Mandatory | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
dataProducerId | ID of the producer registered by DMI for the alternateIDs in the operations in this request. | requestId | Identifier for the overall Datajob | Path | String | Y | ||||
dataProducerJobId | Identifier of the job created by the data producer. | Path | String | Y | dataProducerId | ID of the producer registered by DMI for the alernateIDs in the operations in this request. | (not globally unique) | PathQuery | String | Y |
destination | The destination of the results: Kafka topic name or s3 bucket name. This shall be put into the Kafka message headers returned to NCMP | Query | String | Y |
...