Do you perhaps know from which version this issue exists, then I’ll reinstall to that version and only update once the patch has been released.
I just did a clean install of version 11.0.0-202011171636110752-16ab953d and I’m getting the exact problem. 
Anyone else having this issue?
Any news on this issue?
Just a quick info, would you be able to provide us with output of “cat /proc/cpuinfo” from an executor?
See below, thanks for looking into this again. 
Summary
[root@vdw-executor01 ~]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 8
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 1
cpu cores : 8
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 2
cpu cores : 8
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 8
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 4
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 4
cpu cores : 8
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 5
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 5
cpu cores : 8
apicid : 5
initial apicid : 5
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 6
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 6
cpu cores : 8
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
stepping : 7
microcode : 0xffffffff
cpu MHz : 2600.001
cache size : 20480 KB
physical id : 0
siblings : 8
core id : 7
cpu cores : 8
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni cx16 hypervisor lahf_lm
bogomips : 5200.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
Sorry for asking again but any news on this?
Not sure if I have asked to try this, can you please set the below setting to java and try the query?
click on admin-support-enter below in support key box and click show
exec.preferred.codegenerator set to java (value will be gandiva), save and retry query
Looks like that is working. I’ve installed 4.0, moved my data and then upgraded to 13.1.0. Tried running the query before setting that support setting and it gave the same error as before, after setting it, it completed the queries without any issues.
I’ll let you know if I find any other issues. thank you so much!!