[PR #623] SchedulerEntryID option for registered scheduled job #800

New issue

Open

opened 2026-03-02 06:05:39 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 06:05:39 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hibiken/asynq/pull/623
Author: @ilkerkorkut
Created: 2/28/2023
Status: 🔄 Open

Base: master ← Head: feature/scheduler-entry-id

📝 Commits (2)

7c65581 SchedulerEntryID option for registered scheduled job
f75581d scheduler_test

📊 Changes

3 files changed (+101 additions, -21 deletions)

View changed files

📝 client.go (+27 -13)
📝 scheduler.go (+27 -8)
📝 scheduler_test.go (+47 -0)

📄 Description

Managing autogenerated scheduler job entry ids are very difficult in some cases and it may need costly processes.

Example Scenario: When we try to generate a scheduler job per user basis and wa may want to follow that scheduler job process and unregister on a certain case. So we need to save scheduler job id to on db(need persistency) or cache after that we should check the which user has which scheduler job entry id. So It goes a costly approach. I tried to add SchedulerEntryID Option for Register method.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hibiken/asynq/pull/623 **Author:** [@ilkerkorkut](https://github.com/ilkerkorkut) **Created:** 2/28/2023 **Status:** 🔄 Open **Base:** `master` ← **Head:** `feature/scheduler-entry-id` --- ### 📝 Commits (2) - [`7c65581`](https://github.com/hibiken/asynq/commit/7c65581fd7ac89ecb6ab5c4a59fccd205e61fe6d) SchedulerEntryID option for registered scheduled job - [`f75581d`](https://github.com/hibiken/asynq/commit/f75581d4e27b7c5d5ac7d0c12e6bff5a12abeffe) scheduler_test ### 📊 Changes **3 files changed** (+101 additions, -21 deletions) <details> <summary>View changed files</summary> 📝 `client.go` (+27 -13) 📝 `scheduler.go` (+27 -8) 📝 `scheduler_test.go` (+47 -0) </details> ### 📄 Description Managing autogenerated scheduler job entry ids are very difficult in some cases and it may need costly processes. Example Scenario: When we try to generate a scheduler job per user basis and wa may want to follow that scheduler job process and unregister on a certain case. So we need to save scheduler job id to on db(need persistency) or cache after that we should check the which user has which scheduler job entry id. So It goes a costly approach. I tried to add SchedulerEntryID Option for Register method. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>