tkobayas opened a new issue, #7210: URL: https://github.com/apache/incubator-kie/issues/7210
## Problem The [sequential mode documentation](https://kie.apache.org/docs/10.2.x/drools/drools/rule-engine/index.html#phreak-sequential-mode-con_rule-engine) says: > When you use sequential mode, the Drools rule engine ignores any insert, modify, or update statements in rules. This has been inaccurate since Drools 6.0, when PHREAK replaced RETE. Since then, `modify`/`update` in sequential mode is intentionally supported (DROOLS-650, BZ-1228098). From the [Drools 6.0 release notes](https://docs.drools.org/6.5.0.CR1/drools-docs/html/ch02.html) (§2.13.1): > Sequential mode continues to be supported for PHREAK but now 'modify' is allowed. While there is no 'inference' with sequential configuration, as rules are lazily evaluated, any rule not yet evaluated will see the more recent data as a result of 'modify'. This is more inline with how people intuitively think sequential works. ## What should be updated 1. Remove the statement that sequential mode "ignores" modify/update — it does not. 2. Clarify the actual semantics: each rule evaluates once in salience order; rules not yet evaluated see the current state of facts including modifications made by earlier rules. 3. Note that beta node sharing is automatically disabled in sequential mode (#7201, #7202) to ensure correct behavior with modify/update. 4. The implementation-detail steps (node memory, left-input adapter, Command objects) should be reviewed for accuracy or removed — they describe RETE-era internals and are likely to become stale. ## Related - #7201 — beta node sharing disabled in sequential mode - #7202 — PR for #7201 - #7209 — `@Propagation(IMMEDIATE)` in sequential mode - DROOLS-650 — modify support in sequential mode - BZ-1228098 — eager evaluation disabled for sequential mode -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
