You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Neal Richardson (Jira)" <ji...@apache.org> on 2022/07/15 15:33:00 UTC

[jira] [Assigned] (ARROW-16178) [C++] Add a ThreadLocalState concept built on thread local

     [ https://issues.apache.org/jira/browse/ARROW-16178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neal Richardson reassigned ARROW-16178:
---------------------------------------

    Assignee:     (was: Weston Pace)
      Labels: pull-request-available stop  (was: pull-request-available)

This issue has been inactive for 3 months, so it has been unassigned and marked as unstarted. If you are still working on this, feel free to reassign yourself and resume progress.

> [C++] Add a ThreadLocalState concept built on thread local
> ----------------------------------------------------------
>
>                 Key: ARROW-16178
>                 URL: https://issues.apache.org/jira/browse/ARROW-16178
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: C++
>            Reporter: Weston Pace
>            Priority: Major
>              Labels: pull-request-available, stop
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The ThreadLocalState is tied to an executor and, on creation, creates a state for every thread in the executor.  In order to quickly access a particular thread's state we need a way  to get a thread index (the index of the thread in the executor).  Historically we used ThreadIndexer and this JIRA introduces a new approach using thread local.
> Similar to the ThreadIndexer this thread local state concept will fail when the capacity is resized during a run.
> Similar to the ThreadIndexer this concept won't work too well for serial execution until ARROW-15732 is resolved.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)