Guide to upload a new data-incremental.zip for an incremental load with manual assignment of the data-id.
URL
https://my.<region>.fredhopperservices.com/{sin}/data/input/{id}/data-incremental.zip
Formats
application/zip
HTTP Method(s)
PUT
Requires Authentication
Yes
Parameters
| Parameter | Required | Description |
|---|---|---|
| {sin} | Yes | Name of the service instance, for example fas:live1 or fas:test1. |
| {id} | Yes | Data id |
Response
HTTP "201 Created" response, with the required trigger contents as 'text/plain' body.
Usage example
The following uses curl to upload the input file 'data-incremental.zip' into the service instance 'fas:live1' in the 'us1' region with a data-id of '2012-05-21_12-00-00'.
The command shows the headers returned by the server (-D - parameters) for illustration purposes as well.
Request:
$ curl -s -X PUT -D - --data-binary @data-incremental.zip -H "Content-Type: application/zip" -u user:password https://my.us1.fredhopperservices.com/fas:live1/data/input/2012-05-21_12-00-00/data-incremental.zip HTTP/1.1 201 Created Location: https://my.us1.fredhopperservices.com/fas:live1/data/input/2012-05-21_12-00-00/ Content-Type: text/plain data-id=2012-05-21_12-00-00
|
Checksum Upload Before the new data id can be used for triggering a checksum has to be uploaded using the same approach. Assuming 'data-incremental.zip.md5' is the correctly formatted checksum file for 'data-incremental.zip' the following example uploads it to the same data id: $ curl -s -X PUT -D - --data-binary @data-incremental.zip.md5 -H "Content-Type: text/plain" -u user:password https://my.us1.fredhopperservices.com/fas:live1/data/input/2012-05-21_12-00-00/data-incremental.zip.md5 HTTP/1.1 201 Created Location: https://my.us1.fredhopperservices.com/fas:live1/data/input/2012-05-21_12-00-00/ Content-Type: text/plain data-id=2012-05-21_12-00-00 |
Comments
0 comments
Please sign in to leave a comment.