Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

intent: a status-filtered roll-up (where:) never recomputes on a transition - the child's -transitioned is not a roll-up trigger

Chiusa
  • Qualcosa non va?
#7,942 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #8003 di @nedelcho-delchev-tues — integrata

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
53/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
backend, distributed-systems

Direzione di ricerca

Start with GlueIntentGenerator.java around lines 736–752 to see which child events trigger roll-up recomputation, then trace how transitions publish the -transitioned topic in Transition.java.template. Check EdmIntentGenerator.java around lines 755–800 for the grouping keys involved. Done when a status transition that changes whether a child matches where: causes the parent roll-up to recompute; the issue suggests binding a transition handler or including the filter columns in grouping keys.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

Take a roll-up whose where: filters the child rows by status, for example "sum only the non-voided allocations / documents" (#7542). It does not recompute when a child's status is moved by a transitions: button, a generates sourceStatus: flip or a process setter. The parent keeps counting the row the filter now excludes (or keeps ignoring the one it now includes) until some unrelated -updated of a sibling happens to fire.

Why (release commit 862f6d1a, 14.93.0)

  • A roll-up subscribes to the child's create / -updated / -deleted / -rekeyed topics only (GlueIntentGenerator.java ~L736-L752).
  • A transition writes the status through updateProperties(..., "<...>-transitioned"), which publishes only -transitioned (Transition.java.template, TransitionIntent javadoc).
  • -rekeyed does not cover it either. The grouping keys that trigger it are only the aggregates' by: and the roll-up's via FK (EdmIntentGenerator.java ~L755-L800), never the columns a where: reads.

Expected

When a roll-up has a where:, also bind a <Child>RollupOnTransition handler on the child's -transitioned topic. It is the same idempotent recompute. Alternatively, add the where: columns to the child's grouping keys so the targeted write publishes -rekeyed. Workaround used in BusinessIntents today: route the status change through a plain -updated write (the payment pattern), documented per module.

Related but distinct: #7905 (coalesced roll-ups drop a member's where:), #7869.

Found on 14.88.0 by BusinessIntents (wave 2026-10-17) and re-checked against the 14.93.0 source; still present.

🤖 Generated with Claude Code

Lingua principale
Java
Stelle
278
Fork
97
Merge medio
17h 19m
PR unite (30g)
261

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eclipse-dirigible/dirigible

Tutte le issue di eclipse-dirigible/dirigible

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.