Merge pull request #11 from not-empty/feature-check-status-fix

fixing check status behavior and documentation, adding options on schedule (push to queue)

Author: leodisarli

README.md

@@ -205,7 +205,7 @@ node sample/multi-producer.js default 60 '{"data":"mydata"}'
 
 If you use parallel processing with multiple workers, finding out when all jobs have completed successfully can be a complicated task due to asynchrony.
 
-To deal with this, Taurus has a functionality that uses a Redis + Lua solution to ensure that the last job in a group was executed, to use it you need to increment a list using a unique specific key when sending to each queue, and decrement this key to each queue that runs successfully.
+To deal with this, Taurus has a functionality that uses a Redis + Lua solution to ensure that the last job in a group was executed, to use it you will need to set a unique specific key with the amount of total queues you wanto to excecute, before sending to the queues, and decrement this key to each queue that runs successfully.
 
 The last queue will know it is last and will allow you to perform finishing actions.
 
@@ -218,13 +218,14 @@ AUX_REDIS_HOST=taurus-redis
 AUX_REDIS_PORT=6379
 ```
 
-2) When inserting into each queue you can use the CheckCompletion class to increment each job: (If you are outside the Taurus ecosystem you can just create a key in redis with [INCR command](https://redis.io/commands/incr/) with your favorite language.)
+2) When inserting into each queue you can use the CheckCompletion class to increment each job: (If you are outside the Taurus ecosystem you can just create a key in redis with [SET command](https://redis.io/commands/set/) on your favorite language but the value MUST BE INTEGER greater than 0.)
 
 ```js
 const CheckCompletion = require('../core/check-completion.js');
 ...
+const numberOfJobs = Number (100);
 const checkCompletion = new CheckCompletion();
-await checkCompletion.increment(uniqueKeyToRepresenTheGroup);
+await checkCompletion.setInitialJobCounter(uniqueKeyToRepresenTheGroup, numberOfJobs);
 ```
 
 3) When each queue has finished executing, just call the decrement command and check if it returned zero, if it returned zero, this queue is the last one of this group and you can execute any command you find necessary

core/check-completion.js

@@ -9,15 +9,16 @@ class CheckCompletion {
     };
   }
 
-  async increment(
+  async setInitialJobCounter(
       key,
+      value,
   ) {
     const redis = new Redis(
         this.options,
     );
 
-    const result = await redis.incr(key);
-    console.log(`Job counter key: ${key}, increased, total jobs: ${result}`);
+    const result = await redis.set(key, value);
+    console.log(`Job counter key: ${key}, increased, total jobs: ${value}`);
 
     await redis.disconnect();
     return result;

core/push-queue.js

@@ -43,6 +43,7 @@ class PushQueue {
       queueName,
       data,
       time,
+      options = {},
   ) {
     const queue = new Bull(
         queueName,
@@ -58,6 +59,7 @@ class PushQueue {
           attempts: configQueue.attempts,
           backoff: configQueue.backoff,
           jobId: ulid.ulid(),
+          ...options,
         },
     );