[
https://issues.apache.org/jira/browse/ARROW-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261028#comment-16261028
]
ASF GitHub Bot commented on ARROW-1703:
---------------------------------------
xhochy commented on issue #1334: ARROW-1703: [C++] Vendor exact version of
jemalloc we depend on
URL: https://github.com/apache/arrow/pull/1334#issuecomment-346088573
I'm not sure if we have a free matrix entry anymore where we would be able
to activate it again. I would like to (gradually) reintroduce `jemalloc` as the
default again but we also should keep jemalloc-free builds in our test matrix.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [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
> Assignee: Uwe L. Korn
> Labels: pull-request-available
> 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)
