Describe the unexpected behaviour
Currently in CH, arrayJoin action always processes one input chunk and does transforming, finally output another one chunk. The output chunk is probably huge if serveral arrayJoins are calculated continuously in SQL, which is not friendly for memory limited usages(e.g. gluten)

To avoid OOM, we should respect max_block_size settings while executing arrayJoin