river icon indicating copy to clipboard operation
river copied to clipboard

UniqueOpts with ByTags argument

Open mobiletoly opened this issue 1 year ago • 2 comments

We do have ByArgs argument in UniqueOpts but unfortunately it is not good enough for my use case to describe uniqueness of the job (because I have different timestamps, requests id etc in job arguments). Is it possible to add something like ByTags to UniqueOpts for more fine-grained uniqueness control?

mobiletoly avatar May 22 '24 12:05 mobiletoly

@mobiletoly would it work for your use case if you could do uniqueness comparisons against a subset of args (specified by top level JSON field names) instead of all of them? That’s something we’ve talked about before but haven’t yet got around to implementing.

bgentry avatar May 22 '24 12:05 bgentry

hi @bgentry - yes, it will absolutely work for me.

mobiletoly avatar May 22 '24 13:05 mobiletoly

This should be closed by #590 which will be merged shortly. You can now opt into having uniqueness considerations look at a subset of your job's arguments, instead of all of them.

bgentry avatar Sep 22 '24 19:09 bgentry