We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
too many write operations when uploading files
I am using Elixir wrapper to DropboxAPI to upload files, which is doing simple upload using `files/upload` route. def upload(client, path, file, mode \\ "add", autorename \\ true, mute \\ false) d...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorTo clarify a bit, you need one "upload session" per file. Each upload session gets its own session ID. When adding data to a single upload session, you need to identify how much you've already added to that upload session by using the "offset" value. This helps make sure you're uploading the right pieces. If you specify the wrong current offset for an upload session, you'll get that "incorrect_offset" error.
You can then "finish" up to 1000 files together (i.e., up to 1000 upload sessions) using /2/files/upload_session/finish_batch.
Check the /2/files/upload_session/finish_batch documentation for information on how to format the parameters for it. Be sure to click on "UploadSessionFinishArg", and so on, to expand the documentation for the nested fields.
I also recommend using the API v2 Explorer to help guide you in understanding how to build the parameters. Click the "Add" button to add an entry and fill in the fields, for instance, and then click "Show Code" to see what the resulting code would be for the call.
I don't believe we have a sample for using upload sessions with /2/files/upload_session/finish_batch, but there are some examples of just using upload sessions (with some of the SDKs) here, which should be a good starting point for the logic:
So at first, I ran this in the command line
curl -X POST https://content.dropboxapi.com/2/files/upload_session/start \
--header "Authorization: Bearer PWK08cePo_kAAAAAAAB2oRsQSyGQbQ2qy-SC69zC7G" \
--header "Dropbox-API-Arg: {\"close\": false}" \
--header "Content-Type: application/octet-stream" \
--data-binary @local_file.txtIt returned:
{"session_id": "AAAAAAAbQhipmPJOosGS-Q"}I don't see any offset values here but let's take a look at next request of append.
curl -X POST https://content.dropboxapi.com/2/files/upload_session/append_v2 \
--header "Authorization: Bearer C69zip6zi9bwHgqhYHNYQbrpZ5C7G" \
--header "Dropbox-API-Arg: {\"cursor\": {\"session_id\": \"AAAAAAAbQhipmPJOosGS-Q\",\"offset\": 0},\"close\": false}" \
--header "Content-Type: application/octet-stream" \
--data-binary @local_file.txtIt returned:
{"error_summary": "incorrect_offset/.", "error": {".tag": "incorrect_offset", "correct_offset": 37}}Now I sent the offset value 37 and it gave me null as
curl -X POST https://content.dropboxapi.com/2/files/upload_session/append_v2 --header "Authorization: Bearer SC69zip6zi9bwHgqhYHNYQbrpZ5C7G" --header "Dropbox-API-Arg: {\"cursor\": {\"session_id\": \"AAAAAAAbQhipmPJOosGS-Q\",\"offset\": 37},\"close\": false}" --header "Content-Type: application/octet-stream" --data-binary @local_file.txtit returned: `null`
Now I did finish_batch,
curl -X POST https://api.dropboxapi.com/2/files/upload_session/finish_batch \
> --header "Authorization: Bearer SC69zip6zi9bwHgqhYHNYQbrpZ5C7G" \
> --header "Content-Type: application/json" \
> --data "{\"entries\": [{\"cursor\": {\"session_id\": \"AAAAAAAbQhipmPJOosGS-Q\",\"offset\": 0},\"commit\": {\"path\": \"/Homework/math/Matrices.txt\",\"mode\": \"add\",\"autorename\": true,\"mute\": false,\"strict_conflict\": false}}]}"
It returned to me with async_job_id,
{".tag": "async_job_id", "async_job_id": "dbjid:AACkTPVL8VvaGyrUdEPui0uHg-mzJuroOoZ5yQvP3HB-4JxhpBGNlRrt8XOH6XiOJIpUKlNjUbHtJgUPGWKhQnXm"}on the batch check,
curl -X POST https://api.dropboxapi.com/2/files/upload_session/finish_batch/check --header "Authorization: Bearer SC69zip6zi9bwHgqhYHNYQbrpZ5C7G" --header "Content-Type: application/json" --data "{\"async_job_id\": \"dbjid:AACkTPVL8VvaGyrUdEPui0uHg-mzJuroOoZ5yQvP3HB-4JxhpBGNlRrt8XOH6XiOJIpUKlNjUbHtJgUPGWKhQnXm\"}It returned as
{".tag": "complete", "entries": [{".tag": "failure", "failure": {".tag": "lookup_failed", "lookup_failed": {".tag": "incorrect_offset", "correct_offset": 74}}}]}My question is, from where I can have the offset value? its nowhere from the very start?
I followed the complete documentation guide, and I am not able to even upload one file with upload session.
- Greg-DB
The 'offset' value is "The amount of data that has been uploaded so far. We use this to make sure upload data isn't lost or duplicated in the event of a network error.".
That is to say, it should be the number of bytes that you have already uploaded so far for that particular upload session. You should keep track of this client-side as you send the file data up to Dropbox.
Okay thanks now,
on upload_session/start and then doing upload_session/finish
my file is getting uploaded.
the file was of 37 kbs. which I set in offset in upload_session/finish, but
how upload_session/finish_batch can over all the present sessions? when it only takes one session id? and one one file name?
I can now upload the file to my account using only
upload_session/start and upload_session/finish
would that be enough ? for uploading multiple files at once? to dropbox?
I am actually in a loop which being spawned and sending files to dropbox account.Now I only need to so session start and in the finish add the file size and that it? would that stop sending me too many write operations message?
and If I can the append_v2 with close true, it gives me error as
double the offset, it should be, file as 37KBs and it gives an error as offset should be 74
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
