This message was deleted.

I don't know that this limit can be changed at query time. My understanding is that the limit is used for broadcast objects (e.g. Lookups) as well as loading secondary tables and intermediate results for join operations. I have seen it raised as high as 1m without causing problems, but I think it is highly dependent on how much heap memory you have to spare on your cluster.

Oh ok John. thank you

In the cluster tuning doc page HERE there is some mention of heap sizing for Lookups ... maybe use that as reference.

Ok