[GitHub] [arrow] joosthooz opened a new issue, #33880: Add/improve tracing in the dataset writer

["joosthooz (via GitHub)" <gi...@apache.org>]

joosthooz opened a new issue, #33880:
URL: https://github.com/apache/arrow/issues/33880

   ### Describe the enhancement requested
   
   The telemetry code in the dataset writer currently does not trace the asynchronous tasks that are submitted to the I/O thread pool that perform the actual encoding, compression, and writing.
   
   Follow-up to https://github.com/apache/arrow/pull/33738, where @westonpace noted: "Mentally, when I think of the dataset writer, I think there are two parts. The first part should be the trailing part of the fragment/pipeline that feeds the writer. In this first part we partition the batch, select the appropriate file queues, and deposit the batches into the queues. There is then a separate dedicated thread task to write each batch to the writer."
   
   
   ### Component(s)
   
   C++


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add/improve tracing in the dataset writer [arrow]

["thisisnic (via GitHub)" <gi...@apache.org>]

thisisnic commented on issue #33880:
URL: https://github.com/apache/arrow/issues/33880#issuecomment-3921673420

   This issue has been marked as stale because it has had no activity in the past 2 years. Please remove the stale label or comment below, or this issue will be closed in 14 days.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org