You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Alenka Frim (Jira)" <ji...@apache.org> on 2022/05/12 13:36:00 UTC
[jira] [Updated] (ARROW-16542) [C++] Expose tracing capability in arrow compute engine
[ https://issues.apache.org/jira/browse/ARROW-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alenka Frim updated ARROW-16542:
--------------------------------
Summary: [C++] Expose tracing capability in arrow compute engine (was: Expose tracing capability in arrow compute engine)
> [C++] Expose tracing capability in arrow compute engine
> -------------------------------------------------------
>
> Key: ARROW-16542
> URL: https://issues.apache.org/jira/browse/ARROW-16542
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 8.0.0
> Reporter: Yue Ni
> Priority: Major
>
> I am authoring a custom execution node for arrow compute engine, and currently the built-in execution nodes have the tracing capability integrated (https://issues.apache.org/jira/browse/ARROW-12671), but the tracing API is marked as internal `arrow/util/tracing_internal.h` and cannot be used externally, I wonder if there is any chance this tracing API could be made public, so that custom execution nodes could use the same/consistent mechanism for tracing purpose. Because usually users would like to view the entire execution as a whole, if custom nodes and built-in nodes use two different tracing approaches, that will make analysis more difficult.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)