-
Notifications
You must be signed in to change notification settings - Fork 90
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
UniqueOpts with ByTags argument #368
Comments
@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. |
hi @bgentry - yes, it will absolutely work for me. |
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. |
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?
The text was updated successfully, but these errors were encountered: