[jira] [Commented] (KUDU-1752) C++ client error memory should be bounded
[ https://issues.apache.org/jira/browse/KUDU-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733905#comment-15733905 ] Alexey Serbin commented on KUDU-1752: - Implemented in 60aa54e21b715a4e7a1931570c9736a2c7f211c6 > C++ client error memory should be bounded > - > > Key: KUDU-1752 > URL: https://issues.apache.org/jira/browse/KUDU-1752 > Project: Kudu > Issue Type: Bug > Components: client >Affects Versions: 1.0.0 >Reporter: Matthew Jacobs >Assignee: Alexey Serbin >Priority: Critical > Labels: client, impala > Fix For: 1.2.0 > > > The Kudu client can allocate unbounded amounts of memory for error messages > today, which is a potential problem for processes using the client. The API > to get errors does have a way to indicate the errors overflowed the error > buffer, but this isn't set yet. > Given that error messages can vary significantly in size (as they include a > var length string which will soon also include tracing output) and the row, > the client should have a way to indicate the max buffer memory size rather > than just some number of rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KUDU-1752) C++ client error memory should be bounded
[ https://issues.apache.org/jira/browse/KUDU-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712799#comment-15712799 ] Alexey Serbin commented on KUDU-1752: - In review: https://gerrit.cloudera.org/#/c/5308/ > C++ client error memory should be bounded > - > > Key: KUDU-1752 > URL: https://issues.apache.org/jira/browse/KUDU-1752 > Project: Kudu > Issue Type: Bug > Components: client >Affects Versions: 1.0.0 >Reporter: Matthew Jacobs >Assignee: Alexey Serbin >Priority: Critical > Labels: client, impala > > The Kudu client can allocate unbounded amounts of memory for error messages > today, which is a potential problem for processes using the client. The API > to get errors does have a way to indicate the errors overflowed the error > buffer, but this isn't set yet. > Given that error messages can vary significantly in size (as they include a > var length string which will soon also include tracing output) and the row, > the client should have a way to indicate the max buffer memory size rather > than just some number of rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
