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

Posted to issues@arrow.apache.org by "Uwe L. Korn (JIRA)" <ji...@apache.org> on 2017/11/02 17:25:00 UTC

[jira] [Commented] (ARROW-1703) [C++] Vendor exact version of jemalloc we depend on

    [ https://issues.apache.org/jira/browse/ARROW-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236165#comment-16236165 ] 

Uwe L. Korn commented on ARROW-1703:
------------------------------------

To clear things up a bit: We are not going to use a patched version, simply a non-released version of the {{stable-4.x}} branch.

> [C++] Vendor exact version of jemalloc we depend on
> ---------------------------------------------------
>
>                 Key: ARROW-1703
>                 URL: https://issues.apache.org/jira/browse/ARROW-1703
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.8.0
>
>
> Since we are likely going to be using a patched jemalloc, we probably should not support using jemalloc with any other version, or relying on system packages. jemalloc would therefore always be built together with Arrow if {{ARROW_JEMALLOC}} is on
> For this reason I believe we should vendor the code at the pinned commit as with Redis and other projects: https://github.com/antirez/redis/tree/unstable/deps



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)