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

Posted to issues@impala.apache.org by "Omid Shahidi (Jira)" <ji...@apache.org> on 2022/07/27 20:45:00 UTC

[jira] [Resolved] (IMPALA-9615) Make re2's max_mem option configurable via an Impala startup flag.

     [ https://issues.apache.org/jira/browse/IMPALA-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Omid Shahidi resolved IMPALA-9615.
----------------------------------
    Fix Version/s: Impala 4.2.0
       Resolution: Fixed

> Make re2's max_mem option configurable via an Impala startup flag.
> ------------------------------------------------------------------
>
>                 Key: IMPALA-9615
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9615
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 3.4.0
>            Reporter: Attila Jeges
>            Assignee: Omid Shahidi
>            Priority: Major
>              Labels: backend, ramp-up
>             Fix For: Impala 4.2.0
>
>
> Right now Impala always uses the default max_mem value for re2 regexp pattern matching.
> For more memory consuming patterns this can cause the following error:
> "re2/re2.cc:667: DFA out of memory: size xxxxx, bytemap range xx, list count xxxxx".
> It would be nice if re2's max_mem option would be configurable via an Impala startup flag.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)