Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84EE11199A for ; Sun, 27 Apr 2014 02:12:19 +0000 (UTC) Received: (qmail 50607 invoked by uid 500); 27 Apr 2014 02:12:18 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 50282 invoked by uid 500); 27 Apr 2014 02:12:18 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@spark.apache.org Delivered-To: mailing list issues@spark.apache.org Received: (qmail 50129 invoked by uid 99); 27 Apr 2014 02:12:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Apr 2014 02:12:16 +0000 Date: Sun, 27 Apr 2014 02:12:16 +0000 (UTC) From: "Patrick Wendell (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (SPARK-1622) Expose input split(s) accessed by a task in UI or logs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982163#comment-13982163 ] Patrick Wendell edited comment on SPARK-1622 at 4/27/14 2:12 AM: ----------------------------------------------------------------- I think it would be good to have a general mechanism for RDD implementations to add contextual information for each task that ends up `TaskInfo` and ultimately in the UI. This could include values pinned to a specific task but also counters which can be aggregated across all the tasks in a stage. was (Author: pwendell): I think it would be good to have a general mechanism for RDD implementations to add contextual information for each task that ends up `TaskInfo`. This could include values pinned to a specific task but also counters which can be aggregated across all the tasks in a stage. > Expose input split(s) accessed by a task in UI or logs > ------------------------------------------------------ > > Key: SPARK-1622 > URL: https://issues.apache.org/jira/browse/SPARK-1622 > Project: Spark > Issue Type: Improvement > Reporter: Matei Zaharia > > Right now it's hard to debug which input files or blocks therein have invalid data. The InputSplit for a HadoopRDD is not even exposed programmatically in Scala/Java (it's private[spark]). -- This message was sent by Atlassian JIRA (v6.2#6252)