Major Description
dear Kudu developers,
a string field cost at least 16 bytes in rows data while transferring scan results
i read the source code and found the cpptype for STRING is kudu::Slice ( contains offset and size info ) which always take 16bytes in row data sidecar.
when there are lots of short/null strings in scan result ( very common for my tables ) transferring performance is not ideal. ( compared with scanning parquet)
do you have any plan to optimize this?