You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jin Shang (Jira)" <ji...@apache.org> on 2022/09/19 02:58:00 UTC
[jira] [Assigned] (ARROW-17770) [C++][Gandiva] Fix const correctness of Gandiva projector Evaluate
[ https://issues.apache.org/jira/browse/ARROW-17770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jin Shang reassigned ARROW-17770:
---------------------------------
Assignee: Jin Shang
> [C++][Gandiva] Fix const correctness of Gandiva projector Evaluate
> ------------------------------------------------------------------
>
> Key: ARROW-17770
> URL: https://issues.apache.org/jira/browse/ARROW-17770
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++ - Gandiva
> Affects Versions: 9.0.0
> Reporter: Jin Shang
> Assignee: Jin Shang
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I was trying to figure out the thread-safeness of Gandiva projector evaluation, i.e., whether I can use a single Projector to evaluate multiple inputs concurrently. I assumed it isn't safe because the Evaluate function is not marked const. However, as far as I understand, the Evaluate function merely executes a compiled function on the input, which doesn't modify a project's internal states and should be const.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)