You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Jungtaek Lim (Jira)" <ji...@apache.org> on 2023/04/25 00:37:00 UTC
[jira] [Resolved] (SPARK-43233) Before batch reading from Kafka, log topic partition, offset range, etc, for debuggin
[ https://issues.apache.org/jira/browse/SPARK-43233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved SPARK-43233.
----------------------------------
Fix Version/s: 3.5.0
Assignee: Siying Dong
Resolution: Fixed
Issue resolved via https://github.com/apache/spark/pull/40905
> Before batch reading from Kafka, log topic partition, offset range, etc, for debuggin
> -------------------------------------------------------------------------------------
>
> Key: SPARK-43233
> URL: https://issues.apache.org/jira/browse/SPARK-43233
> Project: Spark
> Issue Type: Task
> Components: Structured Streaming
> Affects Versions: 3.4.0
> Reporter: Siying Dong
> Assignee: Siying Dong
> Priority: Trivial
> Fix For: 3.5.0
>
>
> When debugging some slowness issue in structured streaming, it is hard to map a Kafka topic and partition to a Kafka task. Adding some logging in executor might help make it easier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org