You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "DawnZhang (JIRA)" <ji...@apache.org> on 2017/04/28 11:12:04 UTC

[jira] [Created] (KUDU-1985) optimize result transferring performance for scanning short/null STRING values

DawnZhang created KUDU-1985:
-------------------------------

             Summary: optimize result transferring performance for scanning short/null STRING values
                 Key: KUDU-1985
                 URL: https://issues.apache.org/jira/browse/KUDU-1985
             Project: Kudu
          Issue Type: Wish
          Components: client, tserver
            Reporter: DawnZhang


dear Kudu developers,

a string field cost at least 16 bytes in rows data while transferring scan results
cpptype for STRING is kudu::Slice ( contains offset and size info ) and always take 16bytes in row data sidecar.

when there are lots of short/null strings in scan result transferring via network could be slow. ( compared with scanning parquet)

do you have any plan to optimize this?





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)