ModelEngine-Group / ModelEngine-Group/fit-framework
Waterflow 中条件节点使用场景限制
Open
Nobody has claimed this yet.
from: gitcode
in: waterflow
status: waiting-for-internal-feedback
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 335
- PR merge metrics
- No merged PRs in 30d
Description
比如:
ProcessFlow<Integer> flow = Flows.<Integer>create()
.conditions()
.match(i -> i < 4, node -> node)
.others(node -> node)
.reduce(Integer::sum)
.just(i -> {
System.out.println("result=" + i);
}).close();
flow.offer(new Integer[]{1, 2, 3, 4, 5, 6});
- 每个分支中的数据会被认为是一组数据,条件节点后接reduce的写法,会将每个分支的数据独立汇聚为一个结果。
- 不能启用数据保序,如果启用,数据被分流到不同分支后,数据无法正常运行走下去。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ProcessFlow example using Flows.create(), conditions(), match(), others(), reduce(), and offer(). Reproduce the independent branch aggregation and the failure when ordered data is enabled. The issue does not define the intended behavior or acceptance criteria, so confirm the desired change before modifying the WaterFlow implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100