Kaleb Goulding

BrandonA
Can you clarify what you mean by json_arrayindex accumulating? Are both the first and second Json Input node in the chain performing an Array Retrieve operation?

my first node was a json_input with the second being a python processor that was doing some adjustment to my “path” value. the first work item in the python processor had the json_arrayindex value of 1328, not 0 as I was expecting.


as for the attribute copy crash. I left a few sessions open in attempts to get a proper crash log. they all ended up waking up. so it may not be a crash after all. but is evaluating incredibly slow.

I should also report that using an attribute copy between two json_input nodes is resulting in a consistent crash for me. as well as the json_array index being accumulated when multiple json inputs are chained together. I'm not sure if this was intended, but i expected the counter to reset per node.

thanks for the help Brandon! the json input now processes as expected, and the wildcards in the Query are a fantastic addition. I am still struggling a bit with their outputs. It might be my lack of understanding partitioning. But how would I go about partitioning multiple json inputs? so far i've only been able to get a resulting single work_item.