Find jobs by data
See original GitHub issueHello. I know that getJob will not return a repeatable job. but is there any possibility to get all jobs that have specific data?
Here is an example. I would like to get all jobs that have transactionId=‘jk591k123na’
queue.add('generateAddresses', {transactionId: 'jk591k123na'}, {
jobId: 'jk591k123na',
repeat: { every: 10 * 60 * 1000 }
});
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
DataJobs.com: Analytics Jobs, Hadoop Jobs, DBA Jobs, Data ...
Job board for everything big data - data scientists, DBAs, Hadoop technology, analytics, data analysts. We match rarefied talent with top companies.
Read more >Jobseeker or Worker : U.S. Bureau of Labor Statistics
If you are looking to enter the job market, change jobs, or find career ... charts cover a variety of topics and feature...
Read more >Data Analytics Job Boards
AI-jobs.net: lists freelance positions, part-time and full-time jobs, and internships exclusively in AI and Big Data ; Analytic Talent: national database of jobs...
Read more >17+ Best Data Job Boards (Data Science, Data Analysis, ML ...
Looking for jobs in data science, data analysis, machine learning, artificial intelligence, etc.? Here are the best data job boards to know!
Read more >Data Analyst Jobs | Monster.com
Check out Data Analyst jobs available today on Monster. Monster is your source for jobs & career opportunities.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

could also be useful to find/remove jobs by name- that way if I know I have a specific thing I want to index on (like
transactionId) which is too dynamic to have separate queues for, I could still do something like:(in my use case it’d be tricky to keep track of job ids, since jobs are calling an external api and creating new jobs based on the pagination data returned, which and it’s not predictable how many pages there will be)
@roggervalf thanks. I think I have an elegant way of dealing with this as well.