-
Type:
Improvement
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Streams
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform 11.1.23, nxplatform 11.1.24
-
Story Points:0
There are cases where a processor needs to be defined but not start/stop by the StreamService.
For instance, an import processor can be registered and start/stop using a REST API.
Another case is when having different processors that work together, we may want to initialized all the streams first and then control the order the processors are started.
We can add start flag:
<streamProcessor name="myProcessor" class="org.nuxeo.runtime.stream.tests.MyStreamProcessor" logConfig="default" start="false" >...
Also, some a processor can use source or sink streams defined by other processor and in this case, we don't want to create conflict during initialization (streams being defined by both processor).
We can add an external flag to the stream configuration:
<streamProcessor name="myProcessor" class="org.nuxeo.runtime.stream.tests.MyStreamProcessor" logConfig="default"> <stream name="externalOutput" external="true" /> ...
- is related to
-
NXP-29238 Enable to register a Processor without running it (10.10 Backport)
-
- Resolved
-
-
NXP-29361 Add an option to disable Stream Processing
-
- Resolved
-
-
NXP-28086 Bulk Service should have an option to use an Elasticsearch scroller
-
- Resolved
-
- is required by
-
NXP-28357 Bulk Service Processor should be contributed by configuration
-
- Resolved
-
- Is referenced in