-
Notifications
You must be signed in to change notification settings - Fork 731
Revert "chore: backfill email-domain member organization dates (CM-1107)" #4063
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -58,7 +58,7 @@ export async function blockMemberOrganizationAffiliation( | |
|
|
||
| export async function markMemberForAffiliationRecalc(memberIds: string[]): Promise<void> { | ||
| try { | ||
| await svc.redis.sAdd('recalculate-member-affiliations', memberIds) | ||
| await svc.redis.sAdd('queue:recalculate:members:affiliation', memberIds) | ||
| } catch (error) { | ||
| svc.log.error(error, 'Error marking member for affiliation recalc!') | ||
| throw error | ||
|
|
@@ -67,7 +67,7 @@ export async function markMemberForAffiliationRecalc(memberIds: string[]): Promi | |
|
|
||
| export async function getMembersForAffiliationRecalc(batchSize: number): Promise<string[]> { | ||
| try { | ||
| return svc.redis.sPop('recalculate-member-affiliations', batchSize) | ||
| return svc.redis.sPop('queue:recalculate:members:affiliation', batchSize) | ||
|
Comment on lines
59
to
+70
|
||
| } catch (error) { | ||
| svc.log.error(error, 'Error getting members for affiliation recalc!') | ||
| throw error | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change renames the Redis set key used to queue member IDs for affiliation recalculation. Any members already queued under the old key will no longer be processed (they’ll remain stranded in the old set). Consider reading/draining from both keys temporarily or adding a one-time migration/drain step before switching the producer/consumer to the new key.