[NXP-25097] BAF: Implement first Bulk Processor SetProperty - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: New Feature
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 10.2
Component/s: Bulk, Core

Epic Link:
BAF: Resilient Bulk Actions Framework
Tags:
Upgrade notes:
Hide

Some test classes have been moved under nuxeo-core-io test part. But nuxeo-core-io test module is a dependency of nuxeo-core-test (former location) to enforce backward compatibility.

TransactionalFeature has been moved from nuxeo-core-test to nuxeo-runtime-test. With this move, we no longer need ContainerFeature. This feature has been removed, you can get same behavior by annotating your test class with:

@RunWith(FeaturesRunner.class) @Features(TransactionalFeature.class) @TransactionalConfig(autoStart = false) public class MyTest { ... }

By that, we also introduce two new features: CoreIOFeature and CoreBulkFeature which deploy needed components to use/test the feature.
Show
Some test classes have been moved under nuxeo-core-io test part. But nuxeo-core-io test module is a dependency of nuxeo-core-test (former location) to enforce backward compatibility. TransactionalFeature has been moved from nuxeo-core-test to nuxeo-runtime-test . With this move, we no longer need ContainerFeature . This feature has been removed, you can get same behavior by annotating your test class with: @RunWith(FeaturesRunner.class) @Features(TransactionalFeature.class) @TransactionalConfig(autoStart = false ) public class MyTest { ... } By that, we also introduce two new features: CoreIOFeature and CoreBulkFeature which deploy needed components to use/test the feature.
Sprint:
nxcore 10.2.7, nxcore 10.2.8
Story Points:
8

Description

We need a Stream Processor having a batch policy and being able to run something.
Services should be extensible to be able to run any kind of bulk actions.

We will also implement a BulkSetProperty computation as the first Bulk action.
The action will takes the property xpath and the value to set.

Bulk actions are registered to BulkComponent along with these (potential) metadata:

idempotent: the action on the document can be done multiple time, and so produce the same result on the same document
policy in case of error: continue, abort, move records to an error stream
concurrency in execution: can we process concurrently the doc ids
bulk concurrency: if the action can be done concurrently with another bulk action or not (delete document or move document).