[ https://issues.apache.org/jira/browse/IMPALA-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768816#comment-16768816 ]
Tim Armstrong commented on IMPALA-7833: --------------------------------------- We only hit the JVM out-of-memory because of constant folding right? If we ran it with a non-constant argument or disabled expression rewrites, wouldn't that avoid the JVM OOM? > Audit and fix other string builtins for long string handling > ------------------------------------------------------------ > > Key: IMPALA-7833 > URL: https://issues.apache.org/jira/browse/IMPALA-7833 > Project: IMPALA > Issue Type: Bug > Components: Backend > Affects Versions: Impala 2.11.0, Impala 3.0, Impala 3.1.0 > Reporter: Tim Armstrong > Priority: Critical > Labels: crash, ramp-up > > Following on from IMPALA-7822, there are some other string builtins that seem > to follow the same pattern of having a string size overflow an int passed > into the StringVal constructor. I think in some cases we get lucky and it > works out, but others it seems possible to crash given the right input > values. > Here are some examples of cases where we can hit such bugs: > {noformat} > select lpad('foo', 17179869184 , ' '); > select rpad('foo', 17179869184 , ' '); > select space(17179869184 ); > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org