-
Notifications
You must be signed in to change notification settings - Fork 34
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
Allow top tags
API to return all tags
#55
Comments
Looking into this one. |
Was able to repro on ba8e556, working on a fix. |
Blerg. Nevermind, actually. It looks as though this is by design. The tag top API only returns tags with at least two backing jobs. In the relevant |
WRT the reasoning for setting the limit to 2, I've been trying to recall it exactly. My recollection is that we didn't necessarily want to expose every tag in use, but only those that were used by multiple jobs. In hindsight, I don't have any particular objection to changing this functionality if others feel strongly. That said, I have a feeling this is functionality that's not used particularly much. |
I think the logical thing to do would be to simply return all tags, but you could provide a limit to the |
That seems reasonable to me. Not sure I'll tackle that right now, but instead I'll repurpose this ticket to fit that task. |
top tags
API to return all tags
Original:
We see the tags in redis/ui but when call client.call("tag", "top", offset, count) we always get empty tag list, i.e. {}. That happens in ruby binding and java binding.
Updated:
The
top tags
API is currently only designed to return tags with at least 2 jobs tagged as such. This task is to make the minimum number of backing jobs an argument (with a sane default) to thetop tags
API.The text was updated successfully, but these errors were encountered: