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
where arguments are filter by key start value - so task d1 had got all arguments which should only be passed to task d12, d13, d14, d15 etc. because argument key i.e:
I have noticed bug in CTR - I define CTR with task name mytask and flow:
d1: mytask && d2: mytask && d3: mytask && d4: mytask && d5: mytask && d6: mytask && d7: mytask && d8: mytask && d9: mytask && d10: mytask && d11: mytask && d12: mytask && d13: mytask && d14: mytask && d15: mytask && d16: mytask && d17: mytask && d18: mytask && d19: mytask && d20: mytask
When I pass arguments:
It's not working correctly because i.e. task d1 get all arguments which contains d1 taskId - I analyze CTR code and find this:
.filter(e -> e.getKey().startsWith("app." + taskNameId) || e.getKey().startsWith("app.*."))
where arguments are filter by key start value - so task d1 had got all arguments which should only be passed to task d12, d13, d14, d15 etc. because argument key i.e:
app.d10.0=my-date=2023-01-14
contain taskId - d1.
I think, it should be filter with period:
|| e.getKey().startsWith("deployer." + taskNameId + ".") || e.getKey().startsWith("deployer.*"))
The text was updated successfully, but these errors were encountered: