[
https://issues.apache.org/jira/browse/ARROW-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17662287#comment-17662287
]
Rok Mihevc commented on ARROW-5264:
-----------------------------------
This issue has been migrated to [issue
#21735|https://github.com/apache/arrow/issues/21735] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [Java] Allow enabling/disabling boundary checking by environmental variable
> ---------------------------------------------------------------------------
>
> Key: ARROW-5264
> URL: https://issues.apache.org/jira/browse/ARROW-5264
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Java
> Reporter: Liya Fan
> Assignee: Liya Fan
> Priority: Minor
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> The flag BoundsChecking#BOUNDS_CHECKING_ENABLED determines if boundary
> checking is enabled/disabled in vector/arrow buffer APIs.
> It has significant performance implications, since boundary checking is a
> frequent operation.
> This issue addresses 2 problems with the flag for boundary checking in Java
> API:
> 1. The flag can be determined by an environmental variable:
> ARROW_ENABLE_UNSAFE_MEMORY_ACCESS, in addition to the system properties. The
> system properties have higher priority than the environmental variable.
> 2. There is an old and a new system property for this flag. To disable
> boundary checking, both the old and new properties must be set to true, which
> is undesirable:
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
