You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OneOnEach deploy strategy does not reset iteration cursor on re-initialize #4731
amber/src/main/scala/org/apache/texera/amber/engine/architecture/deploysemantics/deploystrategy/OneOnEach.scala::OneOnEach.initialize replaces available but leaves index at its prior value. A reused instance re-initialized with a new array continues counting from the prior position and may report the new array as exhausted before any element is returned.
How to reproduce?
vals=OneOnEach()
s.initialize(Array(nodeA, nodeB)); s.next(); s.next() // index = 2
s.initialize(Array(nodeC)) // index NOT reset
s.next() // throws IndexOutOfBoundsException — new array has 1 element but index already 2
Activity
Ma77Ball commentedon May 11, 2026
/take
fix: reset iteration cursor in OneOnEach.initialize (#5028)
fix: reset iteration cursor in OneOnEach.initialize (apache#5028)
chore(amber): remove the unused DeployStrategy family (apache#7705)