Why the state in the BulkStatus response is always equal to scheduled

Ahmad_BenMaallem — Mon, 26 Apr 2021 12:53:59 GMT

Hello,

I tested the bulk action in nuxeo based on the doc https://doc.nuxeo.com/nxdoc/1010/bulk-action-framework/. I have succeeded in creating and launching my specific action.

My problem is that the bulkstatus is still on scheduled knowing that my action is complete.

either the following command :

curl -s -X GET "http://localhost:8080/nuxeo/api/v1/bulk/$CMD"  -u Administrator:Administrator  -H 'content-type: application/json' | jq .

return the following response

{
  "entity-type": "bulkStatus",
  "commandId": "9102632b-0c53-41f9-ad45-29580770855e",
  "state": "SCHEDULED",
  "processed": 0,
  "error": false,
  "errorCount": 0,
  "total": 0,
  "action": "myAction",
  "username": "Administrator",
  "submitted": "2021-04-26T13:36:08.763Z",
  "scrollStart": null,
  "scrollEnd": null,
  "processingStart": null,
  "processingEnd": null,
  "completed": null,
  "processingMillis": 0
}

Re: Why the state in the BulkStatus response is always equal to scheduled

Ahmad_BenMaallem — Tue, 27 Apr 2021 11:25:26 GMT

REQUIREMENTS

To work properly, the Bulk Service needs a true KeyValue storage to store the command and its status, there are 2 possibles choices: - Use RedisKeyValueStore if you have nuxeo.redis.enabled=true in your nuxeo.conf. - Use MongoDBKeyValueStore if you are using the MongoDB template. You should not rely on the default MemKeyValueStore implementation that flushes the data on restart.

topic Re: Why the state in the BulkStatus response is always equal to scheduled in Nuxeo Forum

Why the state in the BulkStatus response is always equal to scheduled

Re: Why the state in the BulkStatus response is always equal to scheduled