Re: why impala memory layout is row base

One of the main problems that a columnar internal row batch format solves is interpretation overhead - if you switch based on type/expression/etc once per value, it is quite slow. But if you switch once per vector of values, the overhead is minimized. Impala uses LLVM query compilation to solve th

why impala memory layout is row base

hi, everyone! I find impala row batch is row base(Each row is contiguous memory), but spark presto clickhouse is column base(every column is contiguous memory), Is there any benefit to doing this?