Job IDs? about activejob HOT 6 CLOSED

I agree this should probably be exposed through AJ. It's not so much implementation detail as useful information to track the job in the backend-specific dashboard you'll be using.

Do all backends have a job ID of their own?

from activejob.

Not all backends support JID. E.g. "Resque" does not.

from activejob.

What would AJ add over what’s being provided in the queues? That you’d get a job-id back when enqueuing that you can use to later refer to? How would you refer to it? Manually or something more sophisticated?

On May 19, 2014, at 4:48 PM, Mike Perham [email protected] wrote:

Is this something that should/can be baked into AJ? Rails has Request ID middleware and all ActiveRecords have IDs. Sidekiq jobs all have a JID so the user can follow the path of execution in logs.

As a side note, this is one area where the native API leaks out of the AJ API: the return value of enqueue.

MyJob.enqueue(1)
=> "59c2c1997c3193b3c950cea8"
—
Reply to this email directly or view it on GitHub.

from activejob.

All good questions. No opinion but I'd suggest documenting the return value even if only to say "adapter-specific but may change in a future AJ release".

On May 19, 2014, at 8:24, David Heinemeier Hansson [email protected] wrote:

What would AJ add over what’s being provided in the queues? That you’d get a job-id back when enqueuing that you can use to later refer to? How would you refer to it? Manually or something more sophisticated?

On May 19, 2014, at 4:48 PM, Mike Perham [email protected] wrote:

Is this something that should/can be baked into AJ? Rails has Request ID middleware and all ActiveRecords have IDs. Sidekiq jobs all have a JID so the user can follow the path of execution in logs.

As a side note, this is one area where the native API leaks out of the AJ API: the return value of enqueue.

MyJob.enqueue(1)
=> "59c2c1997c3193b3c950cea8"
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

from activejob.

I’d take a patch for that :)

On May 19, 2014, at 6:08 PM, Mike Perham [email protected] wrote:

All good questions. No opinion but I'd suggest documenting the return value even if only to say "adapter-specific but may change in a future AJ release".

On May 19, 2014, at 8:24, David Heinemeier Hansson [email protected] wrote:

What would AJ add over what’s being provided in the queues? That you’d get a job-id back when enqueuing that you can use to later refer to? How would you refer to it? Manually or something more sophisticated?

On May 19, 2014, at 4:48 PM, Mike Perham [email protected] wrote:

Is this something that should/can be baked into AJ? Rails has Request ID middleware and all ActiveRecords have IDs. Sidekiq jobs all have a JID so the user can follow the path of execution in logs.

As a side note, this is one area where the native API leaks out of the AJ API: the return value of enqueue.

MyJob.enqueue(1)
=> "59c2c1997c3193b3c950cea8"
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

from activejob.

Done #32

from activejob.