[
https://issues.apache.org/jira/browse/ARROW-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647640#comment-16647640
]
Animesh Trivedi commented on ARROW-3493:
----------------------------------------
So, I propose that we
i) rename the variable from "drill.enable_unsafe_memory_access" to
"arrow.enable_unsafe_memory_access"
ii) set the default to false. This can be enabled if user explicitly wants to
debug and check ranges.
iii) document this flag (and perhaps the netty one too) in the Java user
documentation.
If we agree then I will open a pull request.
> [Java] Document BOUNDS_CHECKING_ENABLED
> ---------------------------------------
>
> Key: ARROW-3493
> URL: https://issues.apache.org/jira/browse/ARROW-3493
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Java
> Affects Versions: 0.11.0
> Reporter: Li Jin
> Priority: Major
>
> According to [~atrivedi], BOUNDS_CHECKING_ENABLED has significant implication
> on performance.
> We should document this better and maybe revisit the default value.
> https://github.com/apache/arrow/blob/master/java/memory/src/main/java/org/apache/arrow/memory/BoundsChecking.java
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
