Comments (5)
Oopsie, I totally forgot about that feature. I'll come back to you with a proper implementation / example.
from bull.
Ok. I've had some time to think about this and I've come to the conclusion that the processors
option should not be deprecated.
However, this options' type will change from
export type BullQueueProcessor =
BullQueueProcessorCallback // (job: Job, done: DoneCallback) => void
| BullQueueAdvancedProcessor // { concurrency?: number; name?: string; callback: BullQueueProcessorCallback; }
| BullQueueSeparateProcessor // string
| BullQueueAdvancedSeparateProcessor; // { concurrency?: number; name?: string; path: string; }
to
export type BullQueueProcessor =
BullQueueSeparateProcessor // string
| BullQueueAdvancedSeparateProcessor; // { concurrency?: number; name?: string; path: string; }
@igor-sky there's already an example in the README. Doesn't this work for you?
from bull.
@fwoelffel Before removing processors
property, please, provide an example, how to run job handlers in separate processes (using file name) with decorators approach
from bull.
@fwoelffel Is example available anywhere? Completely stuck on this one, can't sell nest-bull to lead without showing how to use workers in separate process :(
from bull.
Closed by 1dd0303
from bull.
Related Issues (20)
- Bull events + Nestjs request scoped dependencies
- Support BullMQ v5.0.0 HOT 3
- Bull Module not connecting as expected HOT 1
- Missing WorkerOptions types on BullQueueAdvancedProcessor and BullQueueAdvancedSeparateProcessor HOT 2
- options.family is not cast to number if given in REDIS_URL HOT 1
- Bull support for durable request scoped processors. HOT 4
- Give ability to disable job processing in `BullModule.forRoot` method HOT 4
- Mismatch with bull HOT 3
- NestJS Bull appears to be utilizing Upstash Redis unnecessarily. HOT 1
- Controls for nestjs/bullmq processors in request-scoped providers HOT 4
- Ability to accept/reject jobs before being processed HOT 1
- On application shutdown it closes all the queues. If any active job is creating more jobs it will fail. HOT 2
- Parametrized queue names HOT 1
- Windows sandboxed processors broke HOT 4
- When names of the Queue are unknown and provided via Async Config module HOT 4
- "Connection is closed" jest error when using bullmq > 5.1.11 HOT 3
- Issue with @InjectQueue decorator when used in a class that extends another class HOT 2
- Nestjs bull Consumer process() doesn't pick up job from queue to process HOT 1
- Queue Processor Not Closing in E2E Test Modules HOT 1
- Better way to get `QueueEventsListener` method types HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bull.