Skip to content
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

Named jobs #502

Open
enahsor opened this issue Dec 22, 2021 · 4 comments
Open

Named jobs #502

enahsor opened this issue Dec 22, 2021 · 4 comments

Comments

@enahsor
Copy link

enahsor commented Dec 22, 2021

I'm not sure if this is possible with the current API - I have not seen any documentation supporting this. Is there some way to provide a job with an identifier? eg. I schedule a job called upload-stuff and then I'd be able to refer to that job throughout the lifetime of the schedule. I think this would prove super useful. If you do not think so, please let me know why. If you do agree that this would be useful, I'm open to attempting to implement it.

@leirons
Copy link

leirons commented Jan 5, 2022

Ye, i think it would be cool

@LuisHenri
Copy link

You can add tags to the Job:

def tag(self, *tags: Hashable):

You can add multiple Tags, but if you add only one, you could use it as its name by using next(iter(job.tags))

@rocky4546
Copy link

Yep, I have been using tags for a while. It has the ability to set and then find the tags. My tags represent a task and then I can have multiple events associated with that tag and pull up all events with a query. It works great.

@SijmenHuizenga
Copy link
Collaborator

Hi! Totally agree that it is useful to have a human readable name attached to a job. This is what tags are intended for. Is there is anything specific that you would like to achieve that can't be done without tags?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants