You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
First of all, congrats for the library.
Is there a chance to set the job name in a dynamic way?
I mean, the job behaviour is the same, so I can put the definition in a method that I can invoke when starting the node principal process.
But the name has to be different because I have to execute that job multiple times, one for each message I retrieve from a data source.
For example, say I read a table, each record has an identifier (generated by a third party system), I need to start (and schedule) the JOB for each record (according to some conditions). The job name CANNOT be the same otherwise the record created in mongodb is always the same. Job type should be single because the node process can fail and can be restarted (pod).
This is why I am asking if it's possible to set the job name dinamically.
Does it make sense?
Thanks a lot
Alessandro
The text was updated successfully, but these errors were encountered:
Hello.
First of all, congrats for the library.
Is there a chance to set the job name in a dynamic way?
I mean, the job behaviour is the same, so I can put the definition in a method that I can invoke when starting the node principal process.
But the name has to be different because I have to execute that job multiple times, one for each message I retrieve from a data source.
For example, say I read a table, each record has an identifier (generated by a third party system), I need to start (and schedule) the JOB for each record (according to some conditions). The job name CANNOT be the same otherwise the record created in mongodb is always the same. Job type should be single because the node process can fail and can be restarted (pod).
This is why I am asking if it's possible to set the job name dinamically.
Does it make sense?
Thanks a lot
Alessandro
The text was updated successfully, but these errors were encountered: