[ https://issues.apache.org/jira/browse/IMPALA-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-5778. ----------------------------------- Resolution: Fixed Fix Version/s: Impala 2.10.0 IMPALA-5778: clarify --read_size option. Remove BTS_BLOCK_OVERFLOW error code, which is no longer used and referenced --read_size. Improve the flag description. The output is now: -read_size ((Advanced) The preferred I/O request size in bytes to issue to HDFS or the local filesystem. Increasing the read size will increase memory requirements. Decreasing the read size may decrease I/O throughput.) type: int32 default: 8388608 Testing: Tested that Impala built and basic queries could run. Change-Id: I3c20a9d55f89170b11f569c90b7f2949ddbe4211 Reviewed-on: http://gerrit.cloudera.org:8080/7623 Reviewed-by: Tim Armstrong <tarmstr...@cloudera.com> Tested-by: Impala Public Jenkins > Clarify logging around and usage of read_size startup option > ------------------------------------------------------------ > > Key: IMPALA-5778 > URL: https://issues.apache.org/jira/browse/IMPALA-5778 > Project: IMPALA > Issue Type: Bug > Components: Backend > Reporter: Balazs Jeszenszky > Assignee: Tim Armstrong > Fix For: Impala 2.10.0 > > > The following error message: > "Cannot process row that is bigger than the IO size (row_size=X MB, > null_indicators_size=0). To run this query, increase the IO size (--read_size > option)." > https://github.com/cloudera/Impala/blob/cba02a9a8b8cb765f9f4d2884f0a45e9af1bf2c7/common/thrift/generate_error_codes.py#L209-L211 > > , and the read_size option in general, needs to be reviewed to reflect > changes from IMPALA-3200. -- This message was sent by Atlassian JIRA (v6.4.14#64029)